-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: Vulnerability Scanning #524
base: main
Are you sure you want to change the base?
Conversation
fe467c5
to
7878904
Compare
a74e7f3
to
e13204c
Compare
b704196
to
889cab1
Compare
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
- | - | Generic CLI Secret | 8864448 | Makefile | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
9d63cfd
to
bf65380
Compare
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
54cc7af
to
3674aae
Compare
Signed-off-by: jay-dee7 <[email protected]>
3674aae
to
0a3a905
Compare
Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
6de7d72
to
b4bdfa5
Compare
Signed-off-by: jay-dee7 <[email protected]>
b4bdfa5
to
e13c85e
Compare
And add justfile Signed-off-by: jay-dee7 <[email protected]>
Signed-off-by: jay-dee7 <[email protected]>
1eef6b0
to
81b6789
Compare
c5fa93b
to
8d8d201
Compare
Signed-off-by: jay-dee7 <[email protected]>
8d8d201
to
5a2ee4f
Compare
Signed-off-by: jay-dee7 <[email protected]>
3bea451
to
f5940c9
Compare
Signed-off-by: Jasdeep Singh <[email protected]> Signed-off-by: jay-dee7 <[email protected]>
f5940c9
to
f03c7e2
Compare
Motivation & Context:
reason/motivation behind the PR, context of what problem it solves
This PR solves the issue #issue
Description:
describe the change briefly
Types of Changes:
PR Checklist: