Add severity for Veracode SCA hashcode calculation #7140
Merged
Conversation
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
github-actions
bot
added
the
settings_changes
coheigea
force-pushed
the
coheigea/veracode-sca-severity
branch
3 times, most recently
from
820e5e2 to
1a7d531
Compare
coheigea
force-pushed
the
coheigea/veracode-sca-severity
branch
from
1a7d531 to
9143264
Compare
Maffooch
approved these changes
Nov 17, 2022
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.
On re-import, or if de-dup is enabled, it closes all other findings for a given component name/version that don't have a CVE (Veracode premium data). This takes the severity into account, so it doesn't end up closing a critical finding as a duplicate of a Low severity finding.