Scan Detail
A single scan run lives at /projects/:id/scans/:scanId. The header shows its status, branch, scan types, duration, and trigger. While a scan is still running, the page animates and refreshes until it completes.
Findings
Section titled “Findings”The findings produced by this specific scan — not the deduplicated org-wide list, but exactly what this run reported. Filter by severity, status, scan type, and AI verdict, and search by title, rule ID, or file path. Each row links to the full finding detail.
The novelty filter
Section titled “The novelty filter”Findings can be filtered by how they relate to earlier scans of the same branch:
| Option | Shows |
|---|---|
| All | Every finding in this scan. |
| New in this scan | Findings whose fingerprint was not present in the previous scan of this branch. |
| Recurring | Findings also seen in earlier scans. |
Novelty is computed from the same fingerprint used for deduplication — so “new” means a genuinely new issue, not just a re-run.
Dependencies
Section titled “Dependencies”The packages recorded by this scan — a point-in-time snapshot of the project’s dependency set at the scanned commit. The living, org-wide view is the Dependency Inventory.
Engine results
Section titled “Engine results”Each engine that ran reports its own status and duration. If an engine failed, its findings may be missing — the scan’s overall status will reflect the failure.