Skip to content

update 1

8a55619
Select commit
Loading
Failed to load commit list.
Open

updates #7

update 1
8a55619
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Feb 19, 2025 in 11s

10 secrets uncovered!

10 secrets were uncovered from the scan of 91 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 #7: main 👉 master
GitGuardian id GitGuardian status Secret Commit Filename
14473943 Triggered AWS Keys 712dd52 config.ini View secret
14473946 Triggered Generic High Entropy Secret ac6dedf tradinpal/backtest.py View secret
14473948 Triggered Generic High Entropy Secret 4fa99b7 Trading_Pal-main/position_book.py View secret
14473949 Triggered Generic High Entropy Secret fea47bd Trading_Pal-main/Alpaca.py View secret
14473950 Triggered Username Password 712dd52 config.ini View secret
14473951 Triggered Generic High Entropy Secret 9058658 Gpt Agents/TechnicalGpt.py View secret
15310958 Triggered Generic High Entropy Secret 4dd1372 a View secret
14473954 Triggered OpenAI API Key 712dd52 Gpt social/app.py View secret
14473960 Triggered OpenAI API Key 4fa99b7 Trading_Pal-main/agents/newsgpt.py View secret
14473961 Triggered Generic High Entropy Secret 4fa99b7 Trading_Pal-main/streaming.py 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.