Feature/nfg 67 inventory management

[Ahim-Gillamore]

No description provided.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
nufacturing-api	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 29, 2024 8:07am

[gitguardian]

⚠️ GitGuardian has uncovered 40 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
13251731	Triggered	MongoDB Credentials	ee715a8	.env.production	View secret
13251731	Triggered	MongoDB Credentials	1fec80f	.env.production	View secret
13251732	Triggered	Company Email Password	ee715a8	.env.production	View secret
13251732	Triggered	Company Email Password	ee715a8	.env.local	View secret
13251732	Triggered	Company Email Password	ee715a8	.env.staging	View secret
13251732	Triggered	Company Email Password	ee715a8	.env.development	View secret
13251732	Triggered	Company Email Password	1fec80f	.env.production	View secret
13251732	Triggered	Company Email Password	c16cfdc	.env.staging	View secret
13251732	Triggered	Company Email Password	1fec80f	.env.staging	View secret
13251732	Triggered	Company Email Password	1fec80f	.env.local	View secret
13251732	Triggered	Company Email Password	c16cfdc	.env.production	View secret
13251732	Triggered	Company Email Password	1fec80f	.env.development	View secret
13251732	Triggered	Company Email Password	c16cfdc	.env.development	View secret
13251732	Triggered	Company Email Password	c16cfdc	.env.local	View secret
13251732	Triggered	Company Email Password	3db919a	.env.local	View secret
13251732	Triggered	Company Email Password	3db919a	.env.production	View secret
13251732	Triggered	Company Email Password	3db919a	.env.development	View secret
13251732	Triggered	Company Email Password	3db919a	.env.staging	View secret
13251733	Triggered	MongoDB Credentials	ee715a8	.env.development	View secret
13251733	Triggered	MongoDB Credentials	1fec80f	.env.development	View secret
13251734	Triggered	MongoDB Credentials	ee715a8	.env.staging	View secret
13251734	Triggered	MongoDB Credentials	1fec80f	.env.staging	View secret
13251735	Triggered	Generic High Entropy Secret	ee715a8	.env.staging	View secret
13251735	Triggered	Generic High Entropy Secret	ee715a8	.env.local	View secret
13251735	Triggered	Generic High Entropy Secret	ee715a8	.env.production	View secret
13251735	Triggered	Generic High Entropy Secret	ee715a8	.env.development	View secret
13251735	Triggered	Generic High Entropy Secret	1fec80f	.env.local	View secret
13251735	Triggered	Generic High Entropy Secret	1fec80f	.env.development	View secret
13251735	Triggered	Generic High Entropy Secret	c16cfdc	.env.development	View secret
13251735	Triggered	Generic High Entropy Secret	1fec80f	.env.testing	View secret
13251735	Triggered	Generic High Entropy Secret	1fec80f	.env.production	View secret
13251735	Triggered	Generic High Entropy Secret	c16cfdc	.env.staging	View secret
13251735	Triggered	Generic High Entropy Secret	c16cfdc	.env.local	View secret
13251735	Triggered	Generic High Entropy Secret	1fec80f	.env.staging	View secret
13251735	Triggered	Generic High Entropy Secret	c16cfdc	.env.production	View secret
13251735	Triggered	Generic High Entropy Secret	3db919a	.env.production	View secret
13251735	Triggered	Generic High Entropy Secret	3db919a	.env.local	View secret
13251735	Triggered	Generic High Entropy Secret	fa1de0d	.env.testing	View secret
13251735	Triggered	Generic High Entropy Secret	3db919a	.env.staging	View secret
13251735	Triggered	Generic High Entropy Secret	3db919a	.env.development	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.}

[flemton]

Good job, hurray!

[flemton]

Good job, hurray!