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
{{ message }}
Repository navigation
Add grype GH action for testing generated images #4
Security is an important subject that we don't wanna miss on.
New tools are appearing aiming at testing container images for known vulnerabilities. grype
is one, and would be great to add the checking step to our CI after we build our images, and before we upload them to hub.docker.com.
Implemented for review in #101: pre-publication Grype gate for high/critical findings (including unfixed), retained full JSON reports, fresh weekly rebuilds, and behavioral/configuration tests for all three images. No suppressions were added.
The fresh tested images currently have zero high/critical findings and three medium BusyBox-package matches to CVE-2025-60876, reported as unfixed. The PR CI passed; this does not mean the existing Docker Hub tags have been refreshed yet. Keeping the issue open until the change is merged.
Activity
dbpolito commentedon Nov 13, 2026
Implemented for review in #101: pre-publication Grype gate for high/critical findings (including unfixed), retained full JSON reports, fresh weekly rebuilds, and behavioral/configuration tests for all three images. No suppressions were added.
The fresh tested images currently have zero high/critical findings and three medium BusyBox-package matches to CVE-2025-60876, reported as unfixed. The PR CI passed; this does not mean the existing Docker Hub tags have been refreshed yet. Keeping the issue open until the change is merged.