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

Api convention #1795

Merged
merged 4 commits into from
Sep 1, 2023

fix: remove old config

bb9a866
Select commit
Loading
Failed to load commit list.
Merged

Api convention #1795

fix: remove old config
bb9a866
Select commit
Loading
Failed to load commit list.
This check has been archived and is scheduled for deletion. Learn more about checks retention
GitGuardian / GitGuardian Security Checks skipped Sep 1, 2023 in 1s

You tagged this GitGuardian alert as a false positive

4 secrets were uncovered from the scan of 4 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 #1795: api-convention 👉 main
GitGuardian id Secret Commit Filename
7973515 Elliptic Curve Private Key daeac81 kubefirst-kubeconfig View secret
7973515 Elliptic Curve Private Key bb9a866 kubefirst-kubeconfig View secret
7973516 Generic High Entropy Secret daeac81 kubefirst-kubeconfig View secret
7973516 Generic High Entropy Secret bb9a866 kubefirst-kubeconfig 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.

Our GitHub checks need improvements? Share your feedbacks!