Scanner refinements: streaming truncation, configurable resource ceilings, path sanitization#3
Merged
Merged
Conversation
…e/byte ceilings + strict mode; sanitize displayed paths
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.
Round-2 review follow-ups. Streaming cap() (no full-input buffering); configurable TRUST_ISSUES_MAX_BYTES / MAX_FILES / STRICT with a file-count guard (exit 3 in strict mode); non-printable sanitization of displayed paths. Documents that per-file grep-size and internal wall-clock limits aren't portably enforceable in bash (use a sandbox + timeout). Deferred by design: JSON/SARIF output, full-history secret-scan CI (history is currently a single commit), and repo-settings items.