The same engine, not a copy
The page imports the published @iris-code/core package - the analysers, the scoring and the rules that the VS Code extension, the JetBrains plugin and the CLI all share. A score here is the score your editor would show.
We record anonymous usage counts, never your code.
Choose the seeded workspace to explore a multi-file review target with real problems planted in it: a committed Stripe key, SQL built by concatenation, duplicated logic across two files, an MD5 fingerprint, and a file named against the project’s own convention. Fix them and watch the gate respond.
A demo that scripts its own outcome tells you nothing about the product. This one cannot: it has no script to run.
The page imports the published @iris-code/core package - the analysers, the scoring and the rules that the VS Code extension, the JetBrains plugin and the CLI all share. A score here is the score your editor would show.
Push calls the same function the installed pre-push hook decides on, and prints what the hook prints, down to the exit code. Only the git transport is simulated - the pass or fail is real, measured against the policy in the config file you can edit.
Iris Code reads code, it never runs it, so there is no sandbox and nothing to upload: analysis happens in this tab. One request does leave, and only when you open the dependency audit, which sends package names and versions to OSV.dev and never your source. Share a project and it is encoded into the part of the URL after the #, which browsers never send in a request. The link carries your files; we never see them.
Worth saying plainly, so nothing here reads as the whole product.
The editor extension is free for per-file analysis, secrets, security smells and duplicate detection. Enforcement, whole-project scans and the dependency audits are Pro.