Repository navigation
test(support): stop the curl auth-header fixture tripping secret scanners - #365
Merged
Merged
Conversation
…t scanners stop flagging it
eddietejeda
requested review from
rohan-hotdata
and removed request for
a team
October 28, 2026 04:34
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Aikido reports a HIGH leaked_secret in
src/commands/support.rs. It is the redaction test fixturecurl -H "Authorization: Bearer hd_notarealtoken_0001" https://api.hotdata.dev/...: a literal curl auth header matches the scanner's curl-auth-header rule regardless of how fake the token is. The fixture is now assembled at runtime and points at example.com, so no auth-header literal is in the source. Test behaviour is unchanged.