Skip to content
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

♻️Updated the requirements.txt to use the dependency versions #26

Conversation

Minty-cyber
Copy link
Contributor

No description provided.

Copy link

gitguardian bot commented Nov 11, 2024

⚠️ GitGuardian has uncovered 4 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
13006851 Triggered Generic Password 9b3f74e env.example View secret
13006851 Triggered Generic Password 9b3f74e env.example View secret
14273726 Triggered Django Secret Key 9b3f74e env.example View secret
14273726 Triggered Django Secret Key 9b3f74e env.example 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


🦉 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.

@Minty-cyber
Copy link
Contributor Author

@n1rjal could you check it out?

@n1rjal
Copy link
Owner

n1rjal commented Nov 13, 2024

Hi, can you also implement uv in workflow and format the files with black cli @Minty-cyber

@Minty-cyber
Copy link
Contributor Author

Hi, can you also implement uv in workflow and format the files with black cli @Minty-cyber

Sure thing

@n1rjal
Copy link
Owner

n1rjal commented Nov 13, 2024

can you merge the recent main in it and fix the workflow issue here.
Thanks

@n1rjal n1rjal closed this Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants