Container Registry and Software Supply Chain Platform · View 13 of 33 · 3 · Data
Answering question 4
- Maintain the component index and match advisories against it — never rescan the corpus on a schedule
- A new advisory touches roughly 120 of 40,000 artifacts; scan compute scales with that number, not with the corpus
- Stored-but-not-running artifacts are still answered for, because audit asks about them
Partitioning
- Partitioned by ecosystem and component-name prefix, so the query is bounded rather than a full scan
- Base layers are indexed by layer digest, which is what makes base-image fan-out a single fact
- Query budget: p95 ≤ 3 s across the full retained corpus
Honest limits
- Reachability is available for Go, npm and Python; Java is present-only until phase 3, and the determination made is recorded per finding
- CPE-to-purl mapping from NVD is lossy; disagreement between feeds is flagged rather than resolved automatically