search

Priyanshi662 / FunFusion

https://fun-fusion.netlify.app/
MIT License
9 stars 47 forks source link

Added Random Name Generator #338

Closed SohanRC closed 9 months ago

SohanRC commented 9 months ago

Added Random Name Generator which generates random names according to the Gender selected by the user.

Issue No = #328

Random-Name-Generator

netlify[bot] commented 9 months ago

Deploy Preview for fun-fusion ready!

Name Link
Latest commit e12537557511136b65fc284bbafca0a145810523
Latest deploy log https://app.netlify.com/sites/fun-fusion/deploys/65ca668c981da20008faf47b
Deploy Preview https://deploy-preview-338--fun-fusion.netlify.app/
Preview on mobile
Toggle QR Code...

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[bot] commented 9 months ago

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

🔎 Detected hardcoded secret in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/incidents/secrets) | | Generic High Entropy Secret | e12537557511136b65fc284bbafca0a145810523 | Random Name Generator/index.js | [View secret](https://github.com/Priyanshi662/FunFusion/commit/e12537557511136b65fc284bbafca0a145810523#diff-c4f58d4d0a727b2ff9a43c5936e89cab45e14ebd413bd96c346a22228c0b6f06L12) |
🛠 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 secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) 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.

Our GitHub checks need improvements? Share your feedbacks!