Keep the rule's explanation in the report#12
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Tasks created from a Trivy finding said only
Severity: critical · CVE-2017-16042 · CVSS 9.8and a file path — no explanation of what the vulnerability actually is.The rule pruning dropped
fullDescriptionalong withhelp. Buthelpis where scanners repeat the entire advisory (that is what made these reports weigh tens of megabytes);fullDescriptionis the sentence or two that explains the finding — exactly what the reader needs.Keeping it costs almost nothing: on our test repository the payload grows from 21.6 KB to 25.9 KB, against a 30 MB limit.