testing-app-sec-module

[zeeshan1853]

No description provided.

[gitguardian]

⚠️ GitGuardian has uncovered 18 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.

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.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
12815084	Triggered	GitHub App Keys	dbd8576	config-v1.py	View secret
12815085	Triggered	Slack Application Credentials	dbd8576	config-v1.py	View secret
12815086	Triggered	Generic Password	dbd8576	config-v1.py	View secret
12815087	Triggered	Stripe Keys	dbd8576	config-v1.py	View secret
12815088	Triggered	Stripe Keys	dbd8576	config-v1.py	View secret
12815089	Triggered	GitHub App Keys	dbd8576	config-v1.py	View secret
12815090	Triggered	Slack Bot Token	dbd8576	config-v1.py	View secret
-	-	Generic High Entropy Secret	11bfa61	config.js	View secret
12815091	Triggered	Slack App Token	dbd8576	config-v1.py	View secret
12815092	Triggered	Generic Password	dbd8576	config-v1.py	View secret
121658	Triggered	Generic Private Key	dbd8576	config-v1.py	View secret
121659	Triggered	AWS IAM Keys	dbd8576	config-v1.py	View secret
12815093	Triggered	GitHub App Keys	dbd8576	config-v1.py	View secret
121661	Triggered	Google API Key	dbd8576	config-v1.py	View secret
121662	Triggered	Slack Webhook URL	dbd8576	config-v1.py	View secret
12815095	Triggered	Slack Signing Secret	dbd8576	config-v1.py	View secret
121660	Triggered	Amazon MWS Token	dbd8576	config-v1.py	View secret
12815096	Triggered	Generic Password	dbd8576	config-v1.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

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 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.}