Closed guibranco closed 2 months ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
:white_check_mark: Build CEPAberto 4.0.410 completed (commit https://github.com/guibranco/CEPAberto/commit/ba5edfbc87 by @guibranco)
Coverage variation | Diff coverage |
---|---|
Report missing for 46b22a48ba45102e06113c154475e3a41a60ccc9[^1] | :white_check_mark: ∅ |
:rocket: Don’t miss a bit, follow what’s new on Codacy.
Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more [^1]: Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 4.41%. Comparing base (
fd0ebc3
) to head (b7cc5f6
). Report is 4 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
⚠️ GitGuardian has uncovered 3 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.
🔎 Detected hardcoded secrets in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [5444983](https://dashboard.gitguardian.com/workspace/7014/incidents/5444983?occurrence=160720053) | Triggered | Generic High Entropy Secret | 3daeff65a32df12c2c3f8404f48606bad5ddecde | Tests/CEPAberto.Tests/CEPAbertoClientTest.cs | [View secret](https://github.com/guibranco/CEPAberto/commit/3daeff65a32df12c2c3f8404f48606bad5ddecde#diff-9c8fef13f09ea1f1098a957eba172dbb2cab9a3482a4a965bade065bedbdee23L5) | | [5444983](https://dashboard.gitguardian.com/workspace/7014/incidents/5444983?occurrence=160720054) | Triggered | Generic High Entropy Secret | 3daeff65a32df12c2c3f8404f48606bad5ddecde | Tests/CEPAberto.Tests/CEPAbertoClientTest.cs | [View secret](https://github.com/guibranco/CEPAberto/commit/3daeff65a32df12c2c3f8404f48606bad5ddecde#diff-9c8fef13f09ea1f1098a957eba172dbb2cab9a3482a4a965bade065bedbdee23R5) | | [5444983](https://dashboard.gitguardian.com/workspace/7014/incidents/5444983?occurrence=160720632) | Triggered | Generic High Entropy Secret | b7cc5f6d2c6dbbf850c594c9ad24ee7567f11979 | Tests/CEPAberto.Tests/CEPAbertoClientTest.cs | [View secret](https://github.com/guibranco/CEPAberto/commit/b7cc5f6d2c6dbbf850c594c9ad24ee7567f11979#diff-9c8fef13f09ea1f1098a957eba172dbb2cab9a3482a4a965bade065bedbdee23L5) |
🛠 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/secrets-detection-engine/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/ggshield-docs/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 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.