Cloud scanning
Keep connected repositories checked.
Connect a GitHub repository and choose when to scan it. Cloud reports link findings to source lines and retain repository history, trends and dependency information.
Choose what starts a scan.
- Scan triggers
- Both
- Example workspace score
- 84/100
- Result
- Line-linked findings and repository history
What it does
Repository checks that you explicitly connect.
Cloud scanning reads a connected GitHub repository and produces a report for that scan. Findings link back to source lines, with repository history, trends and dependency information available in the report workflow.
You choose whether scans run on pull requests, merges or both. This is separate from local editor analysis: installing Iris Code does not connect your repositories or enable cloud access.
- Run the first scan when you import a repository.
- Choose pull requests, merges or both as scan triggers.
- Read the report and follow findings back to their lines on GitHub.
Why use it
Keep repository evidence beyond a single editor session.
Local feedback helps while you write. Connected scans give you reports tied to changes in the repository you chose to scan.
- Follow a finding back to the code
- A report links findings to their GitHub source lines. You can investigate the code behind the result rather than assessing the repository from a score alone.
- Choose when a repository is checked
- Configure pull-request and merge triggers to suit your workflow. The connection and trigger choice are explicit actions, separate from installing the editor extension.
- Read results over time
- Repository history and trends keep earlier scan evidence available for comparison. A report describes what was scanned, rather than replacing the checks for a later change.
How to use it
Choose the repository, the triggers and the report to inspect.
Cloud scans use the selected personal or team cloud allowance and active project capacity. Repositories start in manual mode. Free users can opt into automatic triggers within the same monthly cloud allowance. Local file checks remain Free.
Sign in and connect GitHub
Open the repository connection flow and authorise the GitHub access needed for the repositories you want Iris Code to scan.
ResultYou can choose from the repositories available through that connection.
Select a repository and scan triggers
Choose pull requests, merges or both when importing the repository. Importing starts the first scan against its default branch.
ResultThe first scan is requested and future scans follow your configured triggers.
Open the completed report
Inspect findings and follow their links to source lines on GitHub. Read the repository history and trends alongside the individual scan result.
ResultYou have repository scan evidence to investigate and discuss with the people reviewing the change.
The capabilities, in detail.
- Cloud scans on connected GitHub repositoriesPro
- Available with Pro or an active Teams seat.
- Per-repository triggers: merges, pull requests, or bothPro
- Available with Pro or an active Teams seat.
- Monthly cloud scan allowancePro
- Available with Pro or an active Teams seat.
- Every finding linked to its line on GitHubPro
- Available with Pro or an active Teams seat.
- Score history, trends, and a dependency audit per repositoryPro
- Available with Pro or an active Teams seat.
- Personal activity and cross-repository audit historyPro
- Available with Pro or an active Teams seat.
Choose your scope
What's included.
- Free
- Local file analysis stays available on Free. Cloud scanning is a separate, explicit opt-in.
- Pro and Teams
- Personal and team cloud allocations are separate. The account shows current limits. All repositories start manual-only; opt into automatic triggers within the same allowance.
Know the boundary
What it doesn't promise.
Cloud scans read connected repository code. Local editor analysis still runs in-process; cloud access is not enabled by installing the extension.
Start here.
Sign in, connect GitHub, select a repository and choose its scan triggers. Importing starts the first scan against the default branch.