Open Issues
The findings page defaults to the Open Issues view — a deduplicated list of unique security findings tracked across all scans.
Navigate here via Data → Findings in the navbar.
How open issues work
A finding is identified by its combination of repository, rule, file path, and code hash. When the same finding appears in multiple scans it is tracked as a single issue with a times_seen counter rather than as separate rows.
When a full scan completes without a previously open finding, it is automatically marked as resolved. If it reappears in a later scan it is re-opened.
Fast-mode scans (scd scan --fast) update times_seen but never resolve findings — a full scan is required for accurate resolved state. Fast-mode scans are shown in yellow in scan lists.
Columns
| Column | Description |
|---|---|
| Severity | CRITICAL / HIGH / MEDIUM / EXPOSURE |
| Rule | Rule ID and name |
| Repository | Which repo the finding is in |
| File | File path and line number |
| Status | Open / Resolved / Excepted |
| Times seen | How many scans have contained this finding |
| First seen | When the finding was first detected |
| Last seen | Most recent scan that contained this finding |
Filtering
Filter by severity, repository, rule, or free text. URL parameters (?severity=critical, ?repo=, ?rule=) allow linking directly to a filtered view — useful for drill-down links from the dashboard.
Finding detail
Click any row to open the finding detail modal.
The modal shows the code snippet, taint source (if taint analysis was active), scan mode, and deep analysis results when available.