Dashboard View
The Code Quality tab in the dashboard presents every static analysis finding as an actionable card — grouped by rule and file, colour-coded by severity, and linked directly to the affected source code so developers can triage and fix issues without leaving the interface.
Summary metrics
At the top of the tab, a severity distribution bar and key counters provide an at-a-glance overview of scan results:
Severity distribution
A colour-coded progress bar showing the proportion of Error, Warning, and Info findings. Each segment is clickable to filter the list to that severity.
Total findings
The overall count of issues detected across all files and rules.
Files scanned
How many source files the scanner analysed, giving a sense of coverage.
Parsing errors
The number of files that could not be parsed, highlighted when non-zero so teams can investigate unsupported or malformed code.
Finding cards
Each finding is displayed as a card with a left border colour-coded by severity — red for errors, orange for warnings, blue for informational. Cards are grouped by rule and file path, so multiple occurrences at different lines appear as a single entry. Each card surfaces:
Rule identifier
The check ID from the analysis engine, including language and category (e.g. python.django.security.injection.sql). Copyable with one click.
Severity and confidence
Colour-coded badges for Error, Warning, or Info severity, alongside a confidence indicator (High, Medium, Low) showing how certain the detection is.
CWE reference
The Common Weakness Enumeration identifier for the finding, with a hover card showing the full description and a direct link to the MITRE database.
Vulnerability message
A description of the issue and how to fix it, displayed in a highlighted box within the card.
File path and line numbers
The exact file location with line numbers for every occurrence. Grouped findings show all affected lines in a single card.
Source links
Direct links to view the affected line in GitHub and to the rule documentation, so developers can inspect the code and understand the detection logic.
Clicking a card opens a detail panel with the full vulnerability description, technical metadata, and quick-copy actions for the rule ID, CWE, file path, and a formatted export of all details.
Filtering and search
The severity segments in the distribution bar act as one-click filters — selecting a segment narrows the list to findings of that severity only. A free-text search box filters across rule identifiers, vulnerability messages, and file paths in real time.
Findings are sorted by severity by default, with errors surfaced first. The result count updates live as filters are applied, so teams always know how many issues remain at each severity level.