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

Test linting #75

Closed
wants to merge 13 commits into from

fix: add package.json files to pass linting

8d41baf
Select commit
Loading
Failed to load commit list.
Closed

Test linting #75

fix: add package.json files to pass linting
8d41baf
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks completed Jan 31, 2024 in 1s

8 secrets uncovered!

8 secrets were uncovered from the scan of 13 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 #75: test-linting 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
9415172 Triggered PostgreSQL Credentials eedab63 .history/packages/db/.env_20240129205939 View secret
9415172 Triggered PostgreSQL Credentials eedab63 .history/packages/db/.env_20240129205954 View secret
9415172 Triggered PostgreSQL Credentials eedab63 .history/packages/db/.env_20240129205243 View secret
9415172 Triggered PostgreSQL Credentials eedab63 .history/packages/db/.env_20240129205937 View secret
9415172 Triggered PostgreSQL Credentials a237556 .history/packages/db/.env_20240129205939 View secret
9415172 Triggered PostgreSQL Credentials a237556 .history/packages/db/.env_20240129205243 View secret
9415172 Triggered PostgreSQL Credentials a237556 .history/packages/db/.env_20240129205954 View secret
9415172 Triggered PostgreSQL Credentials a237556 .history/packages/db/.env_20240129205937 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!