Skip to content

fix(ci): limit Trivy SARIF severities to CRITICAL,HIGH #101

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
marevol merged 1 commit into from
May 21, 2026
Merged

fix(ci): limit Trivy SARIF severities to CRITICAL,HIGH #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .github/workflows/docker.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,11 @@ jobs:
format: sarif
output: trivy-results.sarif
severity: "CRITICAL,HIGH"
# Without this, `format: sarif` causes trivy-action to override
# TRIVY_SEVERITY to include all severities ("Building SARIF report
# with all severities"), which makes `exit-code: 1` fire on
# MEDIUM/LOW findings too — defeating the `severity` filter.
limit-severities-for-sarif: true
# Skip CVEs without an upstream fix. Slim base images frequently
# carry HIGH OS CVEs (libcap2, ncurses-bin, libudev1, ...) that
# have no fixed Debian version yet — gating CI on these would mean
Expand Down