Skip to content

fix(scan-secrets): portable single-quote class + hyphenated key detection#4

Merged
poshan0126 merged 1 commit into
poshan0126:mainfrom
Blur-red:fix/scan-secrets-bsd-grep-and-hyphenated-keys
Jun 12, 2026
Merged

fix(scan-secrets): portable single-quote class + hyphenated key detection#4
poshan0126 merged 1 commit into
poshan0126:mainfrom
Blur-red:fix/scan-secrets-bsd-grep-and-hyphenated-keys

fix(scan-secrets): portable single-quote class + hyphenated key detec…

7e52a9c
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks completed Jun 5, 2026 in 32s

2 secrets uncovered!

2 secrets was uncovered from the scan of 1 commit in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #4: fix/scan-secrets-bsd-grep-and-hyphenated-keys 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
- - GitHub Personal Access Token 7e52a9c hooks/tests/fixtures/scan-secrets/07-block-github-token.json View secret
- - PostgreSQL Credentials 7e52a9c hooks/tests/fixtures/scan-secrets/09-block-conn-string-creds.json View secret

🛠 Guidelines to remediate hardcoded secrets

  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.