Skip to content
This repository was archived by the owner on Nov 23, 2025. It is now read-only.

Merge pull request #5 from TechTorque-2025/devOps

3552f41
Select commit
Loading
Failed to load commit list.
Merged

Dev #6

Merge pull request #5 from TechTorque-2025/devOps
3552f41
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Nov 8, 2025 in 1s

12 secrets uncovered!

12 secrets were uncovered from the scan of 43 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 #6: dev 👉 main
GitGuardian id GitGuardian status Secret Commit Filename
22222409 Triggered PostgreSQL Credentials d306e7c DATABASE_SETUP_GUIDE.md View secret
22222408 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222407 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222408 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222408 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222408 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222408 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222406 Triggered PostgreSQL Credentials d306e7c DATABASE_SETUP_GUIDE.md View secret
22222407 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222409 Triggered PostgreSQL Credentials d306e7c DATABASE_SETUP_GUIDE.md View secret
22222408 Triggered PostgreSQL Credentials d306e7c DATABASE_CONNECTION_SUMMARY.md View secret
22222406 Triggered PostgreSQL Credentials d306e7c DATABASE_SETUP_GUIDE.md 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.