Add fast-check property tests for encoded-payload-redact#137
Merged
Conversation
Fuzzes the three encodings the rule decodes (base64, hex, percent) with random printable-ASCII text long enough to clear each length floor — every such payload should be masked. Adds a counter-property for high-entropy random bytes (hash/binary-blob shape): the base64-encoded form should be left alone because the decoded printable-ratio falls below the 0.85 threshold. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
encoded-payload-redactcovering all three decoders (base64, hex, percent) plus a counter-property for high-entropy bytes.Why this surface
The rule's decision is the product of three knobs — an encoding regex, a length floor, and a decoded printable-ASCII ratio — and the boundaries are the interesting failure mode (a hash that happens to clear the ratio, a payload one char shy of the floor). Property tests give us coverage of those boundaries without us hand-picking every case.
Test plan
bun run preflight— biome, eslint, tsc (src + tests), knip, jest with coverage (1021 tests).🤖 Generated with Claude Code