Ship only the rules the findings reference#8
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.
A scan of a large repository failed to upload with HTTP 413. It had 508 findings — but the merged SARIF was tens of megabytes, because Semgrep and Checkov embed their entire rule catalogue in
tool.driver.rules, thousands of definitions with long help texts, whether or not anything matched.The merge step now keeps only the rules a run's results actually reference, rewrites each result's
ruleIndexto the pruned array, and drops the prose fields (help,fullDescription) while keeping what the backend reads:security-severity(severity mapping),shortDescriptionandhelpUri.Measured on the K repository: 0.6 MB → 50 KB. An unresolvable
ruleIndexis dropped rather than left pointing at the wrong rule.