Azad1

[Azadqur]

No description provided.

[netlify]

✅ Deploy Preview for grand-capybara-6c6bac ready!

Name	Link
🔨 Latest commit	412433d
🔍 Latest deploy log	https://app.netlify.com/sites/grand-capybara-6c6bac/deploys/66d983d4f1744800089b6beb
😎 Deploy Preview	https://deploy-preview-14--grand-capybara-6c6bac.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[gitguardian]

⚠️ GitGuardian has uncovered 8 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
13512808	Triggered	Generic High Entropy Secret	412433d	script.js	View secret
13323878	Triggered	Generic High Entropy Secret	412433d	script.js	View secret
13323879	Triggered	Generic High Entropy Secret	412433d	script.js	View secret
13489732	Triggered	Generic High Entropy Secret	412433d	script.js	View secret
13423573	Triggered	Generic High Entropy Secret	412433d	script.js	View secret
13323880	Triggered	Generic High Entropy Secret	412433d	script.js	View secret
13415994	Triggered	Generic High Entropy Secret	412433d	script.js	View secret
13306091	Triggered	Generic High Entropy Secret	412433d	script.js	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.}

[Azadqur]

Azad