git-secrets
ripsecrets
| git-secrets | ripsecrets | |
|---|---|---|
| 32 | 6 | |
| 12,026 | 784 | |
| 0.6% | - | |
| 1.0 | 6.1 | |
| 20 days ago | 15 days ago | |
| Shell | Rust | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-secrets
-
Fired for leaked credentials. How do I explain this?
Well, this doesn't really happen at places that don't suck. They had no least privilege access to critical secrets and no processes (like pre-commit hooks using git-secrets) to prevent them being committed.
-
Recovering from Accidentally Pushing Sensitive Information to a Remote Git Repository
# macOS brew install git-secrets # Linux git clone https://github.com/awslabs/git-secrets.git cd git-secrets make install
- Managing secrets like API keys in Python - Why are so many devs still hardcoding secrets?
-
If you pay for an API key depending on the amount of requests, is it safe to push your code to GitHub?
You could use Git hooks to prevent someone from being able to author a commit when you suspect there is a secret being committed. In addition to this, you could also perform this check server-side, in case someone did not run their Git hooks for whatever reason. For example, check out git-secrets.
-
Securing the software supply chain in the cloud
git-secrets
-
How to deal with unintended information leakage when using GitHub as your GIT?
Install git-secrets. Go into each of your repos, scan for past mistakes, and add a git-commit hook:
- GitHub Access Token Exposure
-
Security scanning
I agree that code scanning is really important, the best way to convince others is to identify high-risk threats in source code and present them to the decision-makers. For example, scanning Secrets is great for showing how repositories can be a massive vulnerability and identifying some low-hanging fruit, especially in the git history. Attackers are really after git repository access for this reason and there are plenty of open-source or free tools that you can use to illustrate the problem. Git-Secrets, Truffle Hog. These aren't great for a long-term commercial solution, something like GitGuardian is a better commercial tool but if the goal is just to illustrate the problem then finding some high-value secrets with free tools is a good way to convince the security personnel to invest in some solutions. Then the door is open to having more conversations as you have already proven the risk.
-
Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years
I worked for a big startup last year and was on a contract deadline for integrating a vendor framework into a React Native app.
It was taking too long to get a new temp demo license key and GitHub search with clever filters helped me track down a demo key that was recently uploaded to a test repo.
This is also why I use git-secrets in my repos.
https://github.com/awslabs/git-secrets
-
Marking findings as FPs in recurring scans
Under the covers, it is simply looking up an 'ignore' list stored in YML during each scan. If you are building your own, you might also want to see how AWS Labs is doing it in their solution git secrets.
ripsecrets
-
Rust Easy! Modern Cross-platform Command Line Tools to Supercharge Your Terminal
ripsecrets: Find secret keys in your code before committing them to git.
- A command-line tool to prevent committing secret keys into your source code
- Show HN: No Secrets Quickly find sensitive files in your GitHub repo
- sirwart/secrets: A command-line tool to prevent committing secret keys into your source code
-
Secrets: A command-line tool to prevent committing secret keys into your source
interesting that the author defines a list of pre-defined secrets to scan for
https://github.com/sirwart/secrets/blob/main/src/find_secret...
Why no check for AWS keys?
What are some alternatives?
trufflehog - Find and verify secrets
gitleaks - Protect and discover secrets using Gitleaks 🔑
ggshield - Find and fix 360+ types of hardcoded secrets and 70+ types of infrastructure-as-code misconfigurations.
secretlint - Pluggable linting tool to prevent committing credential.
dust - A more intuitive version of du in rust
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
bottom - Yet another cross-platform graphical process/system monitor.
aws-vault - A vault for securely storing and accessing AWS credentials in development environments
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
SecretFinder - SecretFinder - A python script for find sensitive data (apikeys, accesstoken,jwt,..) and search anything on javascript files
Gitrob - Reconnaissance tool for GitHub organizations