History and trends
History
How the estate's headline numbers changed from one clearcutt-verify run to the next. Each run is compared with the policy in force at the time.
Latest run
2026-10-10 16:51 UTC, compared with 2026-10-06 23:30 UTC. 3 runs recorded.
4
Verified images
– no change
2
Failed images
– no change
2
Unverified images
– no change
0
Images on a stale base
✓ -2 since the previous run
4
Bases proven by layer digests
– no change
25
Critical findings
! +1 since the previous run
192
High findings
! +79 since the previous run
4
Images with no vulnerability data
– no change
What changed for each image
The previous run recorded no per-image rows (clearcutt-verify writes them from v0.15), so changes to particular images show once two runs in a row have them.
Verdicts
Trends
One chart per measure, each on its own scale. Finding counts cover only the images that had vulnerability data in that run; a change in how many were scanned moves them too.
Every run
| Run | Images | Verified | Failed | Unverified | Stale | Proven | Claimed | Unresolved | Critical | High | Not scanned | Signatures verified | Reproduced |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-10-10 16:51 UTC estate-report.json | 8 | 4 | 2 | 2 | 0 | 4 | 0 | 0 | 25 | 192 | 4 | 6 | 4 |
| 2026-10-06 23:30 UTC estate-report.json | 8 | 4 | 2 | 2 | 2 | 4 | 0 | 0 | 24 | 113 | 4 | 6 | 4 |
| 2026-10-06 23:14 UTC estate-report.json | 8 | 4 | 2 | 2 | 2 | 4 | 0 | 0 | 24 | 113 | 4 | 6 | 4 |
? means unknown: no image had vulnerability data in that run, or the run didn't count signatures.