Signing-table

[Motormary]

Description

Table for documents

What type of PR is this? (check all applicable)

• 💡 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Steps to QA

Added to documentation?

• 📜 README.md
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
propdock	❌ Failed (Inspect)			Aug 30, 2024 8:24am

[gitguardian]

⚠️ GitGuardian has uncovered 7 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
13331402	Triggered	Generic High Entropy Secret	fe8dcc8	apps/api/src/routes/internal/tripletex/index.js	View secret
13331403	Triggered	Generic High Entropy Secret	fe8dcc8	apps/api/src/routes/internal/tripletex/index.js	View secret
13110627	Triggered	Generic High Entropy Secret	fe8dcc8	apps/api/src/routes/internal/fiken/index.ts	View secret
13110627	Triggered	Generic High Entropy Secret	fe8dcc8	apps/api/src/routes/internal/fiken/index.ts	View secret
13110627	Triggered	Generic High Entropy Secret	fe8dcc8	apps/api/src/routes/internal/fiken/index.ts	View secret
13110627	Triggered	Generic High Entropy Secret	fe8dcc8	apps/api/src/routes/internal/fiken/index.ts	View secret
13110627	Triggered	Generic High Entropy Secret	fe8dcc8	apps/api/src/routes/internal/fiken/index.ts	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.}

[Codehagen]

214 File changes.
Think you need to Stash the changes -> Make a new branch from main -> and import only the table?