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

Debajyotisaha14/refactoring #37

Merged
merged 6 commits into from
May 14, 2024

Merge branch 'debajyotisaha14/refactoring' of https://github.com/Rajd…

c1cdbf4
Select commit
Loading
Failed to load commit list.
Merged

Debajyotisaha14/refactoring #37

Merge branch 'debajyotisaha14/refactoring' of https://github.com/Rajd…
c1cdbf4
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks skipped May 14, 2024 in 1s

You tagged this GitGuardian alert as a test credential

10 secrets were uncovered from the scan of 6 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 #37: debajyotisaha14/refactoring 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
10245642 Triggered Generic Password e41523d src/config/init.rs View secret
10245642 Triggered Generic Password c1cdbf4 src/config/init.rs View secret
10245644 Triggered Generic Password e41523d src/config/init.rs View secret
10245644 Triggered Generic Password c1cdbf4 src/config/init.rs View secret
11014062 Triggered Generic Password e41523d docs/api-docs/openapi.yaml View secret
11014062 Triggered Generic Password e41523d docs/api-docs/openapi.yaml View secret
11014062 Triggered Generic Password e41523d docs/api-docs/openapi.yaml View secret
11014062 Triggered Generic Password c1cdbf4 docs/api-docs/openapi.yaml View secret
11014062 Triggered Generic Password c1cdbf4 docs/api-docs/openapi.yaml View secret
11014062 Triggered Generic Password c1cdbf4 docs/api-docs/openapi.yaml 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.