-
Notifications
You must be signed in to change notification settings - Fork 4
[pre-commit.ci] pre-commit autoupdate #497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 11487171 | Triggered | Generic Password | f6cd9e5 | backend/.env.example | View secret |
| 11487172 | Triggered | Company Email Password | f6cd9e5 | backend/.env.example | 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.
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 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. |
13265ff to
cc71d42
Compare
3443e7d to
49422d3
Compare
cec723f to
01bc5bd
Compare
f1cd4f3 to
0f32f54
Compare
7a6b1c4 to
664ef12
Compare
4ed598c to
54ea291
Compare
8d23c54 to
786395f
Compare
42b130d to
0f9cf82
Compare
a5b433a to
e5b44f4
Compare
9dd5402 to
812a0fe
Compare
f4a947a to
9297a5a
Compare
2076292 to
c404c3f
Compare
3f02c1c to
c571369
Compare
b6fcd37 to
a9ba1f9
Compare
cd04982 to
a8fbddc
Compare
a8fbddc to
f4e28c2
Compare
f4e28c2 to
f3f31fb
Compare
ed83ad3 to
5e11959
Compare
1b6dbf3 to
7925f36
Compare
cd98c72 to
c2dd8ef
Compare
a7d4422 to
e67030d
Compare
e67030d to
2f62d90
Compare
34a2987 to
5146742
Compare
5146742 to
7f5ca29
Compare
439a9fd to
ba0c0ab
Compare
updates: - [github.com/pre-commit/pre-commit-hooks: v5.0.0 → v6.0.0](pre-commit/pre-commit-hooks@v5.0.0...v6.0.0) - [github.com/astral-sh/ruff-pre-commit: v0.12.5 → v0.14.9](astral-sh/ruff-pre-commit@v0.12.5...v0.14.9) - [github.com/pre-commit/mirrors-eslint: v9.22.0 → v10.0.0-beta.0](pre-commit/mirrors-eslint@v9.22.0...v10.0.0-beta.0)
ba0c0ab to
9da913f
Compare
updates: