Skip to content

fix(ci): Trivy CRITICAL gate should fail only on critical vulns #1053

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
ogazboiz merged 1 commit into from
Jun 1, 2026
Merged

fix(ci): Trivy CRITICAL gate should fail only on critical vulns #1053

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
6 changes: 6 additions & 0 deletions .github/workflows/deploy-staging.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,12 @@ jobs:
output: 'trivy-results.sarif'
severity: 'CRITICAL'
exit-code: '1'
# Without this, trivy-action builds the SARIF with ALL severities and
# the exit-code then trips on any vulnerability (e.g. the existing
# HIGH axios advisories) — not just CRITICAL as the step intends.
# Limiting the report to the requested severity makes the gate fail
# only on genuine CRITICAL findings.
limit-severities-for-sarif: 'true'
trivyignores: '.trivyignore'

- name: Upload Trivy scan results to GitHub Security tab
Expand Down
Loading