Add flare-redact to Input Validation & Output Encoding - #150
Open
GravityHaxx wants to merge 1 commit into
Open
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
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.
Adds flare-redact next to the other data-masking entry (data-guardian), following the existing format.
flare-redact is an MIT-licensed, zero-dependency TypeScript library that redacts secrets and PII by reading content rather than field names — it catches the AWS key pasted into a free-text field, not just
passwordproperties. Detectors are checksum-validated (Luhn, mod-97, Verhoeff…) to keep false positives out of logs, patterns are ReDoS-bounded with an adversarial benchmark in CI, releases are npm provenance-signed, and there are one-line pino/winston/Express integrations plus a CLI with SARIF output for CI secret scanning.