History · changes between runs
From 2026-10-19 00:20 UTC to 2026-10-19 00:27 UTC
Each image in the two runs, before and after: its digest, its base, its verdict, and its findings by severity, and how it changed.
How the images changed
0
Rebased
0
Rebuilt
0
Base moved
0
New
0
Gone
9
Same image
0 images changed verdict and 0 images in both runs changed findings; 0 fixable high or critical findings were fixed and 0 were introduced, counted per image; and 0 images changed their package set. Rebased: a new digest from a rebase. Rebuilt: a new digest otherwise. Base moved: the same image, its base more or less current than before. A verdict or findings can change while the image stays the same, when the policy, the evidence, or the advisories do.
Who had findings, before and after
Per severity, the images that had findings in each run and, of the images in both, which have none now and which have some for the first time, each with how it changed. The fixable high and critical findings are named below; the history only counts the rest.
| Severity | Had some before | Have some after | Now none | Newly some | Unknown in one run |
|---|---|---|---|---|---|
| high |
|
| none | none | none |
| medium |
|
| none | none | none |
| low |
|
| none | none | none |
| unknown |
|
| none | none | none |
An image with no vulnerability data in a run is unknown there, not clean.
Fixable findings, by ID
Each fixable high or critical finding either run lists: which images had it, which have it, and where it was fixed or introduced, with how each image changed. A finding gone from an image was fixed, or a VEX statement now covers it.
| Finding | Had it before | Has it after | Fixed in | New in |
|---|---|---|---|---|
| GHSA-6j4f-fj2g-mc7p |
|
| none | none |
| GHSA-mwp4-54f8-5fhr |
|
| none | none |
| GHSA-qhr7-859c-m2p7 |
|
| none | none |
| GHSA-rfgv-xxqx-mfg5 |
|
| none | none |
| GHSA-rgw5-rvv9-x895 |
|
| none | none |
Image by image
No image changed: the same images, digests, bases, verdicts, and findings in both runs.
9 images unchanged
The same digest, base currency, verdict, and findings in both runs, and the same package set where both runs read it: build-go:1, build-node:24, build-python:3.14, catalog:latest, checkout:latest, run-go:1, run-node:24, run-python:3.14, storefront:latest.
? means unknown: the run had no vulnerability data for that image. The history names an image's fixable high and critical findings and counts the rest, so only those are listed as fixed or new. It identifies the package set by a digest, so "changed" says the set differs, not which packages; the latest run's image pages list them. Packages are unknown for an image whose package set wasn't read in one of the runs.