Pin trivy scanner to v0.0.21 #2137
Merged
Conversation
This file contains 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
ciarams87
force-pushed
the
chore/pin-trivy-scanner
branch
from
d6879b5
to
ae0f352
Compare
ciarams87
changed the title
vepatel
approved these changes
Oct 28, 2021
soneillf5
approved these changes
Nov 1, 2021
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.
Proposed changes
All the known vulnerabilities are being reported in the security tab, even if they have no fixes, and it looks to be because of a change made in the trivy action to always report all vulnerabilities in the sarif file (see https://github.com/aquasecurity/trivy-action/pull/73/files).
Pinning the trivy scanner to the previous version resolves the issue.