Skip to content

Fallback regex excerpt is there as a sort of allow rule different fro…

83511d9
Select commit
Loading
Failed to load commit list.
Open

fix(query): various fixes for passwords and secrets queries #8017

Fallback regex excerpt is there as a sort of allow rule different fro…
83511d9
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Apr 2, 2026 in 33s

7 secrets uncovered!

7 secrets were uncovered from the scan of 28 commits 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 #8017: Fixs_to_Passwords_and_Secrets 👉 master
GitGuardian id GitGuardian status Secret Commit Filename
4266022 Triggered Generic Password 88eee32 assets/queries/common/passwords_and_secrets/test/positive38.yaml View secret
- - Generic High Entropy Secret 5d246c4 assets/queries/common/passwords_and_secrets/test/negative64.tf View secret
- - Generic Password 5d246c4 assets/queries/common/passwords_and_secrets/test/negative72.tf View secret
20161077 Triggered Generic High Entropy Secret 745e832 assets/queries/common/passwords_and_secrets/test/positive34.yaml View secret
- - Generic High Entropy Secret 5d246c4 assets/queries/common/passwords_and_secrets/test/negative66.json View secret
- - Generic Password 5d246c4 assets/queries/common/passwords_and_secrets/test/negative73.yaml View secret
4266006 Triggered Generic Password 5d246c4 assets/queries/common/passwords_and_secrets/test/negative32.yaml 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.