You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,7 +139,10 @@ Access control rules:
139
139
- Prioritized CVEs must always sort to the top in `/cves`, regardless of selected sort column.
140
140
- Dashboard chart datasets must apply the same visibility logic as `stat_total_cves`.
141
141
- Severity distribution must classify each visible CVE exactly once so the bucket sum matches `stat_total_cves`.
142
-
- Dashboard payload includes both `priority_cves` and `high_epss_cves`.
142
+
- Dashboard payload includes both `priority_cves` and `high_epss_cves`, plus `fix_first_cves` (ranked actionable list) and `cve_history` (real per-day totals).
143
+
-`stat_open_risk_acceptances` is scoped: sec team sees the global `requested` count; regular users only count RAs they can access (`user_can_access_ra`), so the stat matches the `/risk-acceptances?status=requested` list.
144
+
- The `cve_history` trend is sourced from the `cve_snapshots` table, filled by the daily `cve_snapshot` scheduler job (runs in the single `worker` process only). The `'*'`/`'*'` rows are org-wide counts deduplicated across namespaces; per-namespace rows may count a CVE once per namespace. `count_visible` applies CVSS/EPSS thresholds (always-show CVEs bypass), `count_total` does not.
145
+
-`mttr_by_severity` is a sec-team-only audit metric; the endpoint returns an empty list for non-sec-team users.
0 commit comments