New

[NathanFrait]

No description provided.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
gcm-backend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 30, 2024 4:18pm
gcm-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 30, 2024 4:18pm

[gitguardian]

⚠️ GitGuardian has uncovered 15 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
10001574	Triggered	MongoDB Credentials	f58a3a8	server/removeField.js	View secret
10001574	Triggered	MongoDB Credentials	516b159	server/index.js	View secret
10001574	Triggered	MongoDB Credentials	5631b0b	client/src/Admin/PrivateRoute/PrivateRoute.jsx	View secret
10001574	Triggered	MongoDB Credentials	c0805b6	client/src/Admin/PrivateRoute/PrivateRoute.jsx	View secret
10001574	Triggered	MongoDB Credentials	4c08eaa	client/src/Admin/PrivateRoute/PrivateRoute.jsx	View secret
10001574	Triggered	MongoDB Credentials	c07785b	client/src/Admin/PrivateRoute/PrivateRoute.jsx	View secret
10001574	Triggered	MongoDB Credentials	516b159	server/index.js	View secret
10001574	Triggered	MongoDB Credentials	2f4b70b	client/src/Admin/PrivateRoute/PrivateRoute.jsx	View secret
10001574	Triggered	MongoDB Credentials	153dc5a	client/src/Admin/pages/Edit.jsx	View secret
10001574	Triggered	MongoDB Credentials	153dc5a	client/src/components/athome.jsx	View secret
10001574	Triggered	MongoDB Credentials	153dc5a	client/src/Admin/pages/Edit.jsx	View secret
10001574	Triggered	MongoDB Credentials	293cb86	client/src/components/athome.jsx	View secret
10001574	Triggered	MongoDB Credentials	293cb86	client/src/Admin/pages/Edit.jsx	View secret
10001574	Triggered	MongoDB Credentials	293cb86	client/src/Admin/pages/Edit.jsx	View secret
10001574	Triggered	MongoDB Credentials	1220e15	client/src/components/athome.jsx	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.}

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 5 minutes (more than 100, code: "api-deployments-free-per-day").

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 4 minutes (more than 100, code: "api-deployments-free-per-day").