[ 20º ] - Release/v2.1.0 frontend agree: Frontend policy decline/agree functionality #206
GitGuardian / GitGuardian Security Checks
failed
Feb 2, 2024 in 54s
4 secrets uncovered!
4 secrets were uncovered from the scan of 31 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 #206:
release/v2.1.0-frontend-agree👉main
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9408211 | Triggered | Generic High Entropy Secret | a79919c | src/store/index.js | View secret |
| 9408211 | Triggered | Generic High Entropy Secret | d11b85a | src/store/index.js | View secret |
| 9408211 | Triggered | Generic High Entropy Secret | ea216db | src/store/index.js | View secret |
| 9408211 | Triggered | Generic High Entropy Secret | cc7e7c6 | src/store/index.js | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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!
Loading