[POC] Test gitguardian with fake credentials #801
Closed
GitGuardian / GitGuardian Security Checks
completed
Oct 18, 2024 in 26s
3 secrets uncovered!
3 secrets were uncovered from the scan of 5 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 #801:
antonymilne-patch-1👉main
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 14157696 | Triggered | MongoDB Credentials | a99773b | README.md | View secret |
| 14200722 | Triggered | AWS Keys | 942edc4 | CODE_OF_CONDUCT.md | View secret |
| 14200722 | Triggered | AWS Keys | 8055938 | CODE_OF_CONDUCT.md | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the secret, review where it is currently used and what would be the impact of revoking/rotating the secret.
- Revoke or rotate the secret.
- Log in to GitGuardian and follow remediation guidance.
To avoid such incidents in the future, consider
- Following these best practices for managing and storing secrets.
- Installing pre-commit secret detection to catch secret before it leaves your machine.
If you have any questions or feedback, please reach out to us on #gitguardian slack channel.
🦉 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.
Loading