Iris Code
FeaturesPlaygroundMCPTeamsPricingDocs
Get Iris Code Free
Sign inGet Iris Code Free
Iris Code

Score every file. Stop the bad ones shipping.

Product
FeaturesPricingTeamsPlaygroundCompare
Surfaces
CLIMCP for agentsLanguagesDownloadVS Code MarketplaceOpen VSXJetBrains Marketplace
Learn
DocsGetting startedHealth scoreGit hooks.irisconfig.jsonCLI reference
Company
AboutBlogChangelogExtended trialsContactSupportX / Twitter
Legal
SecurityPrivacy PolicyTerms of ServiceJetBrains Plugin EULA
© 2026 Iris Code — built by David Jaja.v1.28.0

Getting started

Start where you plan to use Iris Code.

Iris Code has two different first-run paths. Choose the browser for repository-wide cloud scans, or the extension for local feedback while you code.

Iris Code Cloud · About 4 minutes

Scan a GitHub repository in your browser

Connect one repository, run the first audit, then review the exact commit Iris Code measured.

You finish with: A saved, commit-specific report with health, findings, coverage, and scan status. Future pull requests and default-branch pushes can be scanned automatically.

GitHubselected repo
→
Temporary scansource discarded
→
Browser reportcommit pinned

Data boundary: Opt-in cloud scan. Iris Code temporarily reads the selected repository on its infrastructure. Source is discarded after analysis; the report keeps paths, scores, rules, and line numbers.

  1. 01

    Sign in and open Projects

    Create or open your Iris Code account, then choose Projects in your personal account. Team owners can follow the same path inside a team.

    Open your projects

    Expected resultYou arrive at the repository list, not an empty generic dashboard.

  2. 02

    Connect GitHub

    Choose repository, select Connect GitHub, and grant the Iris Code GitHub App access only to the repositories you want available for import.

    Expected resultIris Code can list the repositories covered by that GitHub App installation.

  3. 03

    Choose a repository and rules

    Select one repository. If it contains .irisconfig.json, that committed policy wins. Otherwise choose a saved config or a built-in preset such as Balanced.

    Expected resultThe confirmation names the repository, default branch, policy, and the scan that will be used.

  4. 04

    Import and audit

    Confirm Import and audit. The first scan starts immediately against the current commit on the default branch and uses one scan from your allowance.

    Expected resultThe project moves through queued and running to a completed report—or shows an actionable failure instead of a false score.

  5. 05

    Review the report

    Start with Overview, then open Findings. Every finding belongs to the scanned revision; source links point back to that exact GitHub commit so the evidence cannot drift.

    Expected resultYou know what failed, where it lives, which rule fired, and whether the report covers the full repository.

  6. 06

    Return through Audit history

    Open Audit history in your account to find completed, failed, queued, running, or cancelled scans across every connected repository. Activity keeps local scans and enforcement signals separate.

    Expected resultYou can return to the exact repository and commit without searching through projects one at a time.

Need the deeper reference?

The docs cover installation edge cases, supported languages, configuration, hooks, CLI, and CI.

Open the documentation