Skip to content

remove B2B IPC

GitGuardian / GitGuardian Security Checks failed Apr 29, 2024 in 6s

5 secrets uncovered!

5 secrets were uncovered from the scan of 46 commits in your pull request. ❌

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

Details

πŸ”Ž Detected hardcoded secrets in your pull request

  • Pull request #677: qr-codes πŸ‘‰ master
GitGuardian id GitGuardian status Secret Commit Filename
10282361 Triggered Generic High Entropy Secret 428dd7e backend/pennclubs/settings/development.py View secret
9451515 Triggered Generic Password 50b9c0b .github/workflows/cdkactions_build-and-deploy.yaml View secret
9451515 Triggered Generic Password 03214af .github/workflows/cdkactions_build-and-deploy.yaml View secret
9451515 Triggered Generic Password 80e8201 .github/workflows/cdkactions_build-and-deploy.yaml View secret
10282361 Triggered Generic High Entropy Secret 40fb7f7 backend/pennclubs/settings/ci.py 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.

Our GitHub checks need improvements? Share your feedbacks!