Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore/configuring ci for test prod and cypress cloud record key failure part ii #5

Open
wants to merge 32 commits into
base: main
Choose a base branch
from

Chore (GitHub actions): updating secrets GITHUB TOKEN

6f5edfc
Select commit
Loading
Failed to load commit list.
Open

Chore/configuring ci for test prod and cypress cloud record key failure part ii #5

Chore (GitHub actions): updating secrets GITHUB TOKEN
6f5edfc
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Jun 21, 2024 in 31s

5 secrets uncovered!

5 secrets were uncovered from the scan of 32 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 #5: chore/configuring-ci-for-test-prod-and-cypress-cloud-record-key-failure-part-II 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
10228469 Triggered Generic Password 0587817 .github/workflows/cypress-local.yml View secret
10228469 Triggered Generic Password 478b08d .github/workflows/cypress-local.yml View secret
10228469 Triggered Generic Password 9b67546 .github/workflows/cypress-local.yml View secret
10228469 Triggered Generic Password 22d87cc .github/workflows/cypress-local.yml View secret
10228469 Triggered Generic Password 43553a7 .github/workflows/cypress-local.yml 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.