search

punyakrit / social-share

ShareHub is a Project where users can create their public viewable profile containing their customizable social links and important links that they want to share with the world. Also having option to see their page Analytics
https://www.sharehub.xyz/
MIT License
18 stars 38 forks source link

Enhanced background #121

Closed naisargi17 closed 3 weeks ago

naisargi17 commented 3 weeks ago

I had changed the website design .

https://github.com/punyakrit/social-share/assets/111778403/c941f05f-a05a-47c2-834b-5eeaec403175

vercel[bot] commented 3 weeks ago

@naisargi17 is attempting to deploy a commit to the punyakrit's projects Team on Vercel.

A member of the Team first needs to authorize it.

gitguardian[bot] commented 3 weeks ago

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

🔎 Detected hardcoded secrets in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [-](https://dashboard.gitguardian.com/workspace/350917/incidents/secrets) | | Google OAuth2 Keys | ca0964da23bc1ccacfcab828b6a4d0b7311ec232 | .env.example | [View secret](https://github.com/punyakrit/social-share/commit/ca0964da23bc1ccacfcab828b6a4d0b7311ec232#diff-a3046da0d15a27e89f2afe639b25748a7ad4d9290af3e7b1b6c1a5533c8f0a8cR2) | | [-](https://dashboard.gitguardian.com/workspace/350917/incidents/secrets) | | Google OAuth2 Keys | 7ec379fe01209598483dd3cd4288ef4cb313f27d | .env.example | [View secret](https://github.com/punyakrit/social-share/commit/7ec379fe01209598483dd3cd4288ef4cb313f27d#diff-a3046da0d15a27e89f2afe639b25748a7ad4d9290af3e7b1b6c1a5533c8f0a8cL2) |
🛠 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](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 these secrets](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/specifics/google_oauth2_prefixed#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.

punyakrit commented 3 weeks ago

@naisargi17 your env is public