search

TechNodes2-0 / ElectiveHub

ElectiveHub is an Education Management System designed to simplify and enhance the management of student information and elective subject selection in educational institutions. It offers a suite of applications for students, teachers, and administrators, providing a user-friendly platform.
https://electivehub.onrender.com
MIT License
75 stars 115 forks source link

added a google login button #175

Closed jaydoshi2 closed 6 months ago

jaydoshi2 commented 6 months ago

Current behavior

Proposed changes

Checks

vercel[bot] commented 6 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
elective-hub ❌ Failed (Inspect) May 16, 2024 8:28am
netlify[bot] commented 6 months ago

Deploy Preview for chipper-cucurucho-7e07f5 ready!

Name Link
Latest commit 25ec9e6330ca4788dc524c42227ff020d476f064
Latest deploy log https://app.netlify.com/sites/chipper-cucurucho-7e07f5/deploys/6645c389e0165b0008797c26
Deploy Preview https://deploy-preview-175--chipper-cucurucho-7e07f5.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 6 months ago

⚠️ GitGuardian has uncovered 4 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/355185/incidents/secrets) | | Google OAuth2 Keys | 24cb249f68f9eddc2b84adea0810c3746c67566c | server/app.js | [View secret](https://github.com/TechNodes2-0/ElectiveHub/commit/24cb249f68f9eddc2b84adea0810c3746c67566c#diff-65890f102baa526da3cc5d65e0528ea728fa9fa63659a7f2e1d523686240359cL19) | | [-](https://dashboard.gitguardian.com/workspace/355185/incidents/secrets) | | Google OAuth2 Keys | daac84b0009d23b5d9a4b487d07b8d1c35875efa | server/app.js | [View secret](https://github.com/TechNodes2-0/ElectiveHub/commit/daac84b0009d23b5d9a4b487d07b8d1c35875efa#diff-65890f102baa526da3cc5d65e0528ea728fa9fa63659a7f2e1d523686240359cL19) | | [-](https://dashboard.gitguardian.com/workspace/355185/incidents/secrets) | | Google OAuth2 Keys | f8582ae1f3bebd2a59a1423113deabaf7a5bea9a | server/app.js | [View secret](https://github.com/TechNodes2-0/ElectiveHub/commit/f8582ae1f3bebd2a59a1423113deabaf7a5bea9a#diff-65890f102baa526da3cc5d65e0528ea728fa9fa63659a7f2e1d523686240359cR19) | | [-](https://dashboard.gitguardian.com/workspace/355185/incidents/secrets) | | Google OAuth2 Keys | 24cb249f68f9eddc2b84adea0810c3746c67566c | server/app.js | [View secret](https://github.com/TechNodes2-0/ElectiveHub/commit/24cb249f68f9eddc2b84adea0810c3746c67566c#diff-65890f102baa526da3cc5d65e0528ea728fa9fa63659a7f2e1d523686240359cR19) |
🛠 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.