Repository navigation
ci(security): make trivy, npm audit and cargo audit blocking on PRs - #905
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This was referenced Nov 5, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Follow-up to #839. Trivy, npm audit and cargo audit ran on PRs but with
continue-on-error: true, becausemainstill had high/critical findings. #901 and #904 cleared or baselined those findings, so the three jobs now block on pull requests, matching Semgrep.Feature Summary
trivy,npm-auditandcargo-auditfail the PR on high or critical findingsTechnical Implementation
.github/workflows/security-gates.yml:continue-on-error: truebecomescontinue-on-error: ${{ github.event_name != 'pull_request' }}on the three jobs, the same expression Semgrep already uses. Stale "does not block yet" comments replaced..trivyignoreandcontracts/.cargo/audit.toml(RUSTSEC-2026-0387, [contracts] Resolve RUSTSEC-2026-0387 (crypto-bigint) from soroban-sdk 22 tree #902).mainruleset's required checks, so a red result shows as a failed check but does not by itself stop a merge. Adding them to the ruleset is a separate repo-settings change.Test Coverage
Checked against current
mainbefore flipping:npm audit --audit-level=high: backend, frontend, scripts exit 0cargo auditincontracts/: exit 0fs --scanners vuln,secret,misconfig --severity HIGH,CRITICAL --ignore-unfixed --exit-code 1on a clean export ofmain: exit 0./scripts/ci-local.sh guards: passChecklists
General
./scripts/ci-local.sh <area>and it passes.github/THREAT_MODEL.mdattached and maintainer review requested