Skip to main content
Code can look finished while it still contains a leaked password, a risky pattern or a function nobody can follow. That happens more easily when a coding assistant writes a lot of code quickly. Iris Code checks your code for these problems and shows which parts need attention, whether you wrote the code yourself or used an AI assistant. You choose the project standards and decide whether failed checks should stop a push or a build. It works in your editor, from the terminal and in automated checks that run when code is pushed. Findings can include passwords left in code, risky security patterns, repeated code and functions that are difficult to follow.
Iris Code does not try to tell whether code was written by AI, and it never sends your code to an AI model. Checks in the editor, in the CLI (the commands you type in a terminal), in Git hooks and in CI all run in your own environment.Cloud scans are the exception, and only if you turn them on. They temporarily copy a GitHub repository you choose, delete that copy after the scan and keep the report.

Words used throughout

A finding is one thing Iris Code reports about your code. A blocker is a serious finding; a warning is something to review. A threshold is a limit you set, such as a minimum health score or a maximum number of secrets. The gate compares a scan with those limits and decides whether the code passes. Whether a finding is labelled a blocker or a warning does not, on its own, decide that result. See the terminology page for other terms used in the product.

Quick Start

Install Iris Code and read your first score, in about two minutes

Try the Playground

Edit a sample project in your browser and see the real Iris Code gate block or pass a pretend push

What it finds

Health scores, secrets, duplicate code and risky security patterns

Blocking bad code

Checks before a push and in CI that stop code below your threshold

Terminal and CI

The same checks from a terminal or an automated pipeline, with @iris-code/cli

Configuration

One settings file, committed to your project, so the whole team uses the same thresholds

Iris Code Pro

Whole-project scans, hooks, checks for known security problems in packages, and the full CLI

What you get

A score on every file, on every save. Each file gets a health score from 0 to 100. Long functions, deeply nested code, leftover debug prints and hardcoded values lower it. The score updates by itself when you save. Secrets caught before they ship. If a real API key is written into a file, the sidebar flags it and hides its value. This is free on every plan and needs no setup. Copy-paste made visible. When the same block of code appears in three files, Iris Code reports all three places and can open them side by side. A gate you turn on when you are ready. First, preview how your project scores against six presets, which are ready-made sets of standards. When the result looks right, a pre-push hook (a check Git runs before each push) or a CI step stops anything below your threshold.

How it works

1

Install the extension

Install Iris Code from the Marketplace. It is free, and its icon appears straight away in the Activity Bar, the strip of icons down the side of the editor.
2

Open a file

Open a JavaScript, TypeScript, Vue, Svelte, Go, Python, Ruby, C#, Java or Rust file. Its score appears in the sidebar, with the findings below it. You do not need to set anything up.
3

Preview what would be blocked

At the bottom of the File tab, click Preview Gate. It shows how your code scores against every preset, without changing anything.
4

Turn on blocking

Install the pre-push hook, or add iris gate to CI, the automated checks that run on your code after a push. Code below your threshold is then stopped before it ships.

Your code stays on your machine

The checks run inside your editor, on your machine. Nothing you scan in the editor or the CLI is uploaded, and no AI model reads it. Iris Code does use the network for a few specific things:
  • signing in and checking your licence
  • looking up package versions and known security advisories for the packages your project uses
  • anonymous product-use events, which you can turn off in your account settings
None of these requests carry source code, file contents or project structure. Keeping the checks on your machine gives you three things:
  • Instant feedback - results in milliseconds when you save, with no wait for a server.
  • Offline use - file checks and CLI commands work without a connection.
  • Privacy - private code, secrets and unreleased features stay on your machine.
The one exception is a cloud scan, which you have to switch on. If you connect a repository through the Iris Code GitHub App, the scanner copies that repository’s code from GitHub so it can check it without your editor open. The code is checked and then deleted; only the report is kept. Your code is never run, and no AI model sees it.If you connect nothing, this does not apply, and the editor and the CLI behave exactly as described above. See Cloud overview for what is fetched, stored and deleted.

Languages

Iris Code checks the languages below. The code inside Vue and Svelte files is checked as JavaScript or TypeScript, and ERB templates are checked as Ruby.

Free or Pro

Free includes file scores, clickable findings, secrets detection and Gate Preview. Signing in adds a monthly allowance of project actions, such as a workspace scan, and a separate allowance of cloud scans. Free allowances explains what counts as new work, what you keep afterwards and how team limits work. Pro removes the Free monthly limit on the local project work it covers. It also adds checks that run every time and can stop a push, a build or a CI run.

Free

  • File scores, complexity, findings, secrets and security checks
  • One-file safe fixes and refactor plans
  • Project rules for coding agents, and package checks before installation
  • Verification integrity: a warning when a change skips or deletes tests or loosens your rules
  • Schema structure and focused-file import information
  • Signed-in custom configuration, including scoring weights
  • New workspace, folder and changed-file scans within your allowance
  • Separate dependency audits and multi-file plans within that allowance
  • A separate allowance for cloud repositories you choose to connect, scanned when you ask or, if you opt in, on each merge or pull request
  • Findings, TODOs, maps and shareable reports you already earned, even after your allowance runs out
  • Free Teams with shared allowances and limits on active collaborators and projects

Iris Code Pro

  • Local project work beyond the Free monthly actions, where it applies
  • Checks that can stop a Git push, a build or a CI run
  • A separate paid cloud allocation
  • Existing paid Git history and batch workflows
  • Paid Team seats when your team needs Pro capabilities
You can request a 14-day Pro trial, with no card required. How trials work →