RTDEV-101452 - Stop publishing TruffleHog raw secrets as evidence - #100
Merged
Merged
Conversation
selalererjfrog
approved these changes
Oct 1, 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
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
Raw/RawV2(and secret-bearingExtraData) still present, so anyone who can read the package could read credentials that had only been in the scanned tree.Redacted, verification status). The Markdown report no longer prints the raw secret, and the workflow deletes the unsanitized JSONL beforejf evd create.Test plan
python3 -m unittest test_sanitize_trufflehog.pyinexamples/trufflehog(allowlist, markdown without raw secrets, redacted-echoes-raw, fixture credentials absent fromtrufflehog.json)Trufflehog evidence integration examplestill attaches evidence, and the predicate does not containRaworRawV2Made with Cursor