Fix Integrated Wordlist for Sensitive Content#356
Merged
Conversation
f9db856 to
8912624
Compare
z-maisel
approved these changes
Mar 26, 2026
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.
Note
Low Risk
Low risk: only changes how the sensitive-content fingerprints file is sourced, falling back to an embedded default when no path is provided.
Overview
discover pageno longer hardcodes a default--sensitive-content-fingerprints-path; the flag is now optional and described as custom-only.Sensitive content detection now loads fingerprints from the provided file path when set, otherwise reads the built-in embedded
discover/page/sensitive_content_fingerprints.jsonviaconfigs.ReadFile, ensuring sensitive-content detection works out of the box.Written by Cursor Bugbot for commit 8912624. This will update automatically on new commits. Configure here.