Dashboard
The dashboard aggregates metrics from all scan history into a single view. Every number is derived from your local scan database — no external service is queried. The page loads on startup and refreshes when you navigate to it.
Overall Risk Score
The large number at the top of the dashboard — the Overall Risk Score — is the average of all quantum risk scores across every scan that produced one (Binary, Certificate, and Network scans). Code scans do not contribute to this number because they report per-finding severity rather than a unified 0–100 score.
| Score range | Color | Meaning |
|---|---|---|
| 76 – 100 | Red | Critical — immediate action required |
| 50 – 75 | Orange | High risk — plan migration within 1–2 years |
| 25 – 49 | Yellow | Medium risk — monitor and plan |
| 0 – 24 | Blue | Low risk |
The progress bar below the score visualizes the same value. If no scans with risk scores exist yet, the score shows 0.
Key Metric Cards
Total Analyses
Total number of scan records in the database across all analyzer types. Includes every completed scan — code, binary, certificate, and network.
- In last 24h — scans with a timestamp within the past 24 hours
- Trend arrow — percentage change in scan count comparing the current 7-day window to the previous 7-day window. Green arrow = more scans this week, red = fewer.
Total Findings
Sum of all findings across all scans. How each analyzer contributes:
| Analyzer | What counts as a finding |
|---|---|
| Code (OpenGrep) | Each rule match — one entry in enriched_findings |
| Binary | Each pattern signature match from the binary pattern scan results |
| Certificate | 1 finding if the certificate is Shor-vulnerable (shor_vulnerable: true) |
| Network | Number of open ports found (openPorts array length) |
The Critical and High badges below the count show findings at those severity levels from code scans only (Binary/Certificate/Network findings don't carry per-finding severity labels).
PQC Vulnerabilities
Count of findings classified as quantum-related, shown in purple. Classification logic:
- If the finding's metadata has
quantum_vulnerable: true— counted as PQC - Otherwise, if the message or rule ID contains the word "quantum" — counted as PQC
- All Certificate and Network findings are always counted as PQC
The sub-label shows general security issues — findings that didn't match the PQC classification (SQL injection, XSS, path traversal, etc. from All Security scan mode).
This Week
Number of scans in the last 7 days, with a comparison to the previous 7-day period shown below.
Findings by Severity
Horizontal bar chart showing the distribution of findings across severity levels. The bar width is proportional to each level's share of the total. The count appears inside the bar if it's wide enough, and always on the right.
| Row | Source |
|---|---|
| Critical | Code findings with severity ERROR or CRITICAL |
| High | Code findings with severity WARNING or HIGH |
| Medium | Code findings with severity MEDIUM |
| Low | Code findings with severity LOW, INFO, or anything else |
| Clean | Files/scans with zero findings. For code scans: the clean_files_count stored separately. For binary/certificate/network scans with a risk score of 0 or no findings: counted as 1 clean scan. |
Analyzer Cards
Four clickable cards — one per analyzer. Clicking navigates directly to that analyzer. Each card shows:
| Field | What it means |
|---|---|
| Analyses badge | Total number of scans run with this analyzer |
| Findings | Total findings from this analyzer across all scans (same counting logic as Total Findings above) |
| Last scan date | Timestamp of the most recent scan with this analyzer. Not shown if no scans exist yet. |
Scan type to analyzer mapping:
| DB scan type | Analyzer card |
|---|---|
code_analysis | Code Analyzer |
quantum | Certificate Analyzer |
port | Network Analyzer |
binary | Binary Analyzer |
Recent Activity
The last 10 scans across all analyzers, ordered by most recent first. Each row shows:
| Field | What it means |
|---|---|
| Icon | Analyzer type (Brain = Code, Binary chip = Binary, Shield = Certificate, Network = Network) |
| Target | The scanned path, domain, or filename. Truncated if long. |
| Timestamp | When the scan was run, formatted as local date and time. |
| Findings badge | Number of findings. Red (destructive) if > 0, grey if clean. |
| Risk score | The 0–100 quantum risk score, color-coded by range. Only shown for Binary, Certificate, and Network scans. Not shown for Code scans. |
Clicking a row navigates to the relevant analyzer and loads that specific scan result.
Trend Calculation
The percentage trend shown on the Total Analyses card is calculated as:
trend = ((scans_last_7d - prev_period_scans) / prev_period_scans) × 100Where prev_period_scans is the count of scans in the 7-day window immediately before the current 7-day window (i.e. days 8–14 ago). If there were no scans in the previous period, no trend arrow is shown.
Data Scope
All metrics are scoped to the current user's scan history only — no data from other users is included. The dashboard queries the local SQLite database directly; no network requests are made to external services.