Potential fix for code scanning alert no. 1: Cleartext logging of sensitive information - #10
Merged
Merged
Conversation
…sitive information Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
sanskarIN
marked this pull request as ready for review
September 26, 2026 10:35
… sensitive information' Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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.
Potential fix for https://github.com/sanskarIN/RepoDNA/security/code-scanning/1
The safest fix is to stop logging the full
secretsdata structure in panic messages. Keep the assertion behavior the same (fail if no matching secret is found), but change the error message to include only non-sensitive context (for example, expected rule/path and a count of available findings), rather than{:?}dump of all entries.In
crates/repodna-app/tests/fixtures.rs, update the closure insuspicious_secrets()around line 232:panic!("{rule} in {path}: {secrets:?}")secretscontents, e.g.panic!("missing expected secret finding: rule={rule}, path={path}, findings_count={}", secrets.len())No new imports, methods, or dependencies are needed.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.