Findings and severity
Documentation Index
Fetch the complete documentation index at: https://docs.sourcery.ai/llms.txt
Use this file to discover all available pages before exploring further.
Every scanner produces findings with the same fields. Each finding has a severity, a status, and a group. Those three are all you need to find your way around Issues.
Severity
Section titled “Severity”Each finding has a severity score from 0 to 100, which the dashboard buckets into levels:
| Level | Score range |
|---|---|
| No risk | 0 |
| Low | 1–34 |
| Medium | 35–69 |
| High | 70–89 |
| Critical | 90–100 |
The score combines the rule’s base risk with your repository’s risk profile. The same rule can have different severities in different repositories. See set a repository’s risk profile. You can also override the severity on a finding when you’d rank it differently.
Status
Section titled “Status”A finding has one of these statuses:
| Status | Meaning |
|---|---|
| Active | Detected on the latest scan and not set aside |
| Snoozed | Set aside until you unsnooze it |
| Ignored | Marked as needing no action |
| Solved | Not detected on the latest scan |
Sourcery sets active and solved from scan results. You set snoozed and ignored, from triage.
Sourcery matches findings between scans by fingerprint. Moving the flagged code to another line keeps the same finding. When a scanner finishes, Sourcery marks solved every open finding from that scanner that the run didn’t report. If a scanner times out, its findings keep their status. A finding that a later scan reports again goes back to active, unless an ignore rule covers it, and its activity records it as redetected.
Grouping
Section titled “Grouping”Sourcery groups similar findings by default. A rule that fires in many files shows as one row instead of dozens. Turn off the Group issues toggle on the issues view to see every finding on its own.