Skip to main content
A shareable report turns a saved scan into a picture or PDF that someone can read without opening an editor, such as a manager, a client or a pull request reviewer. It shows the project’s health score and what was checked. The card leaves out code, file paths, secret values and the names of vulnerable packages, so it is safe to post. The PDF can include more detail if you choose it.

Export a saved scan

In VS Code or JetBrains, select the download icon in the Iris Code sidebar header. You can also run Iris Code: Share Report from the VS Code command palette or the JetBrains Tools > Iris Code menu, or select Share report on the Workspace tab after a scan. In the dashboard, select a completed cloud scan and use Share report beside its summary. The preview offers Portrait, Landscape, Save PNG, Save SVG, Save PDF, Copy image and a caption with alternative text for the image. Both Free and paid accounts can export scans they have already run without running them again. A fresh project scan uses your local project allowance or paid access. A report describes the files as they were at the time of the scan, so check its date and what it covered before treating it as a picture of your current files. The portrait card is 1080 by 1350 pixels; landscape is 1200 by 675. Both use embedded fonts. SVG is a vector image that stays sharp when resized, and PDF provides the supporting pages you select, with continuation pages when needed.

Read the numbers

The health score is the same whole-project score shown where the scan ran, such as the editor or the dashboard. The six card tiles count shipped code, which is the code your users run. Counts from test and example files are labelled separately. Tests are test files. Examples are demo and sample code in folders such as examples, demos, samples, playgrounds, integrations or sandbox. Neither changes the shipped-code tiles. The band legend shows all three score ranges in their own colours: green for 80-100, amber for 60-79 and red for 0-59. The range that contains the scan’s score is filled. Not checked means that the scan cannot establish a count. It never means zero. Saved cloud scans currently lack some of the coverage and threshold information needed by this report, so those fields stay Not checked even when the findings list is empty. Passes its own standard or Below its own standard appears only when the exact configuration used for the scan is committed in that repository. Local settings and defaults do not establish that verdict. Static analysis reads the code; it does not run the program or its tests, and the score does not prove that the program is correct.

Choose what to share

The PDF pages section is always visible. Each dialog opens with Full selected and Include file names off. These choices affect the PDF; portrait and landscape cards keep the same content. Summary is ticked and locked. Selecting or clearing another page makes a custom selection; an exact match to Summary or Full activates that button again. The standard’s continuation pages always travel with that section, and page numbers have no gaps. Score trend needs more than one saved scan. Dependencies needs a saved dependency audit and is off in every preset. Selecting it includes package names, versions, statuses and advisory IDs on separate PDF pages. Statuses use the Dependencies table colours: red for vulnerable, amber for outdated, green for up to date and grey when the status is unknown. Each advisory ID links to its public page on OSV.dev. Unavailable pages are disabled with a reason; an export also tells you if a requested page was left out. Where to look groups low-scoring areas and duplicated blocks by folder. Select that page to enable Include file names, which adds relative file names. Cards always omit file paths and package identities. Source code and secret values stay out of all formats. Every report states the saved scan’s date, the Iris Code version and, where known, where the code came from, such as a Git commit. A report made from a downloaded copy of the code says so rather than claiming a Git commit. Score trend appears only when saved history supplies a comparison.

Export from the terminal

iris report is the command for making a report in a terminal, and HTML remains its default format. Use --evidence <evidence-id> to export a saved result as HTML, an image or a PDF; the evidence ID identifies that saved scan. Existing anonymous introductory cards and PDFs remain available. Requesting a fresh directory scan is separate work under Free allowances.
The PDF defaults to Full. Summary writes iris-report-summary.pdf, Full writes iris-report.pdf, and a custom selection writes iris-report-custom.pdf unless you supply --output. Each unavailable requested page prints a reason to stderr without changing a successful exit code. --pages with HTML, PNG or SVG exits with code 2. The command prints the output location after the export succeeds. The existing HTML output remains available for a single-file report.