Skip to content

chore: mark secret-scan fixtures as fake for external scanners#6

Merged
poshan0126 merged 1 commit into
mainfrom
chore/scanner-safe-fixtures
Jun 12, 2026
Merged

chore: mark secret-scan fixtures as fake for external scanners#6
poshan0126 merged 1 commit into
mainfrom
chore/scanner-safe-fixtures

Conversation

@poshan0126

Copy link
Copy Markdown
Owner

Summary

Follow-up to #5 — this commit was pushed to the branch moments after the merge, so it missed the train. Remediates the GitGuardian alerts on the scan-secrets test fixtures (which are deliberate fakes used to prove the hook blocks secrets):

  • .gitguardian.yaml ignores hooks/tests/fixtures/** so future scans skip them
  • Connection-string fixture defanged to fake_user:fake_password_for_tests@localhost
  • CONTRIBUTING codifies the rule: fixture fakes must be unambiguous; never a real credential, even revoked

Test plan

  • bash hooks/tests/run-all.sh — 68/68 (hook still blocks the defanged string)

GitGuardian flagged the scan-secrets test fixtures on PR #5. They are
the deliberate attack samples that prove the hook blocks secrets —
nothing real. Make that machine- and human-obvious:

- .gitguardian.yaml ignores hooks/tests/fixtures/**
- conn-string fixture now uses fake_user:fake_password_for_tests@localhost
  (the GitHub-token fixture already uses an alphabet token)
- CONTRIBUTING: fixture fakes must be unambiguous; never a real
  credential, even revoked
@poshan0126
poshan0126 merged commit ccf6ab2 into main Jun 12, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant