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

Feature/203 links and branding #652

Open
wants to merge 15 commits into
base: develop
Choose a base branch
from

Conversation

sudheer-rk
Copy link
Contributor

No description provided.

@sudheer-rk sudheer-rk self-assigned this Aug 22, 2022
@gitguardian
Copy link

gitguardian bot commented Aug 22, 2022

⚠️ GitGuardian has uncovered 11 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 Secret Commit Filename
1065342 Generic High Entropy Secret 3e151a0 .env.development View secret
1065341 Generic High Entropy Secret 3e151a0 .env.production View secret
1065342 Generic High Entropy Secret e87af02 .env.development View secret
1065341 Generic High Entropy Secret e87af02 .env.production View secret
1065342 Generic High Entropy Secret 7026240 .env.development View secret
1065341 Generic High Entropy Secret 7026240 .env.production View secret
1065342 Generic High Entropy Secret 45b0c53 .env.development View secret
1065341 Generic High Entropy Secret 45b0c53 .env.production View secret
1065342 Generic High Entropy Secret ddb4e2f .env.development View secret
1065341 Generic High Entropy Secret ddb4e2f .env.production View secret
1065342 Generic High Entropy Secret ddb4e2f netlify.toml 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

1 participant