Added license file for frontend/src/ee directory #2120
Conversation
Added license file for frontend/src/ee directory
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9605380 | Triggered | Generic Private Key | ea9bd8a | backend/e2e-test/routes/v3/secrets-v2.spec.ts | View secret |
| 9605380 | Triggered | Generic Private Key | ea9bd8a | backend/e2e-test/routes/v3/secrets-v2.spec.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
Description 📣
I am adding a license file to the frontend/src/ee directory to ensure compliance with the licensing terms specified in the backend/src/ee directory.
Type ✨
Tests 🛠️
I verified the content of the license file to ensure it matches the license in backend/src/ee/LICENSE.md