ci: limit Trivy to vulnerability scanning (scanners: vuln)#174
Merged
Conversation
The Trivy step ran the default vuln+secret scanners, and secret scanning flagged an example OpenSSH private key embedded in a third-party library docstring (autobahn's cryptosign module, a transitive dep via daphne) as a HIGH AsymmetricPrivateKey finding, failing the job. This is a false positive, not a real secret leak or CVE. Set scanners: vuln so the step does what its name implies — scan the image for HIGH/CRITICAL OS/library vulnerabilities only. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Problem
The
trivyjob in the Security workflow has been failing onmain. The failure is not a CVE — Trivy's default scanners arevuln,secret, and the secret scanner flagged:That "key" is an example Ed25519 OpenSSH private key in a docstring of
autobahn'scryptosignmodule (a transitive dependency viadaphne). It is a documentation sample, not a real secret — a false positive. OS/library vulnerability counts are0.Fix
Add
scanners: "vuln"to the Trivy step so it only scans for HIGH/CRITICAL vulnerabilities (matching the step's name and intent). Secret scanning — which only tripped on this third-party docstring — is disabled for this image scan.Notes
severity,exit-code,ignore-unfixedunchanged.🤖 Generated with Claude Code