fix(security): correct false npm-audit claim + SHA-pin Trivy + gate HIGH#31
Merged
Conversation
…mage CVEs) Self-correction: the prior commit raised Trivy to CRITICAL,HIGH, which turned CI red on CVE-2026-33671 (picomatch ReDoS, HIGH, fixed) bundled in the node:22 image's own npm — a base-image CVE the template can't remediate. Revert the gate to CRITICAL (the deliberate original setting), fix the rationale comment to not reference the nonexistent npm-audit step, and align the docs (SECURITY.md, README) to CRITICAL. The Trivy SHA-pin and the removal of the false 'npm audit on every push' claim are kept.
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
1 participant
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.
No description provided.