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

Fix product #91

Open
wants to merge 269 commits into
base: main
Choose a base branch
from
Open

Fix product #91

wants to merge 269 commits into from

Conversation

MUNYESHURImanzi
Copy link
Collaborator

No description provided.

sevelinCa and others added 30 commits June 3, 2024 14:48
iamfrerot and others added 29 commits June 16, 2024 16:01
Copy link

gitguardian bot commented Jul 3, 2024

⚠️ 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 GitGuardian status Secret Commit Filename
11050043 Triggered PostgreSQL Credentials 5061e64 .github/workflows/node.js.yml View secret
11050043 Triggered PostgreSQL Credentials 5061e64 .github/workflows/node.js.yml View secret
11050043 Triggered PostgreSQL Credentials 5061e64 .github/workflows/node.js.yml View secret
11132330 Triggered Generic High Entropy Secret 5061e64 .github/workflows/node.js.yml View secret
11388110 Triggered PostgreSQL Credentials dc0282a .env.example View secret
11388110 Triggered PostgreSQL Credentials 85903d1 .env.example View secret
11388110 Triggered PostgreSQL Credentials ca7dce0 .env.example View secret
11388110 Triggered PostgreSQL Credentials 81c1d1f .env.example View secret
11388110 Triggered PostgreSQL Credentials dfc3c74 .env.example View secret
11388110 Triggered PostgreSQL Credentials 5365c87 .env.example View secret
11388110 Triggered PostgreSQL Credentials f540cef .env.example 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.

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

Successfully merging this pull request may close these issues.