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

[#185355611] added github actions to run dependency check #21

Merged
merged 1 commit into from
Apr 11, 2024

[#185355611] added github actions to run dependency check

2e70f69
Select commit
Loading
Failed to load commit list.
Merged

[#185355611] added github actions to run dependency check #21

[#185355611] added github actions to run dependency check
2e70f69
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks completed Apr 11, 2024 in 0s

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.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #21: fix-github-actions-185355611 👉 master
GitGuardian id GitGuardian status Secret Commit Filename
10274247 Triggered Generic Password 2e70f69 .github/workflows/build-test-java-app.yml View secret
10274247 Triggered Generic Password 2e70f69 .github/workflows/build-test-java-app.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.

Our GitHub checks need improvements? Share your feedbacks!