⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🔎 Details of the secret
| Secret | Commit | Filename | Detected At | |
| ------------------------- | ---------------- | --------------- | -------------------- | -------------------- |
| Generic High Entropy Secret | b1fdac6d5be91beb4878a968c484c8902f4ad217 | assets/js/gitconfig.js | 20:40 January 9th, 2022 | [View secret](https://github.com/austinslatey/concert-scout/commit/b1fdac6d5be91beb4878a968c484c8902f4ad217#diff-434f2be0da172595ea50b3842cd872ebL2) |
| Generic High Entropy Secret | b1fdac6d5be91beb4878a968c484c8902f4ad217 | assets/js/gitconfig.js | 20:40 January 9th, 2022 | [View secret](https://github.com/austinslatey/concert-scout/commit/b1fdac6d5be91beb4878a968c484c8902f4ad217#diff-434f2be0da172595ea50b3842cd872ebL5) |
🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices.
3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment).
4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials
- install [secret detection on pre-commit](https://docs.gitguardian.com/internal-repositories-monitoring/integrations/git_hooks/pre_commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.
GitGuardian is an automated secrets detection service.We help developers and security teams secure the modern software development process.
Kyler-Mclachlan
commented
2 years ago
⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.
Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.
🔎 Details of the secret
| Secret | Commit | Filename | Detected At | | | ------------------------- | ---------------- | --------------- | -------------------- | -------------------- | | Generic High Entropy Secret | b1fdac6d5be91beb4878a968c484c8902f4ad217 | assets/js/gitconfig.js | 20:40 January 9th, 2022 | [View secret](https://github.com/austinslatey/concert-scout/commit/b1fdac6d5be91beb4878a968c484c8902f4ad217#diff-434f2be0da172595ea50b3842cd872ebL2) | | Generic High Entropy Secret | b1fdac6d5be91beb4878a968c484c8902f4ad217 | assets/js/gitconfig.js | 20:40 January 9th, 2022 | [View secret](https://github.com/austinslatey/concert-scout/commit/b1fdac6d5be91beb4878a968c484c8902f4ad217#diff-434f2be0da172595ea50b3842cd872ebL5) |
🛠 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/internal-repositories-monitoring/integrations/git_hooks/pre_commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.
GitGuardian is an automated secrets detection service.We help developers and security teams secure the modern software development process.
Our GitHub checks need improvements? Share your feedbacks