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

Add E-commerce Order Processing with Inventory and Shipment Tracking #633

Closed
wants to merge 7 commits into from

fixed changes

1a7842e
Select commit
Loading
Failed to load commit list.
Closed

Add E-commerce Order Processing with Inventory and Shipment Tracking #633

fixed changes
1a7842e
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks failed Oct 14, 2024 in 33s

6 secrets uncovered!

6 secrets were uncovered from the scan of 7 commits in your pull request. ❌

Please have a look to GitGuardian findings and remediate in order to secure your code.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

Details

🔎 Detected hardcoded secrets in your pull request

  • Pull request #633: contribute2 👉 dev
GitGuardian id GitGuardian status Secret Commit Filename
- - Generic High Entropy Secret 9db2958 cookbooks/ecommerce_order_processing.py View secret
- - Generic High Entropy Secret ec7a9fe cookbooks/Ecommerce_Order_Processing.ipynb View secret
- - Generic High Entropy Secret ec7a9fe cookbooks/ecommerce_order_processing.py View secret
- - Generic High Entropy Secret 9b6495d cookbooks/Ecommerce_Order_Processing.ipynb View secret
14144714 Triggered Generic Password 88b6004 deploy/simple-docker-compose.yaml View secret
14144715 Triggered Generic Password 88b6004 deploy/simple-docker-compose.yaml 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.