trufflehog
Find, verify, and analyze leaked credentials (by trufflesecurity)
git-secrets
Prevents you from committing secrets and credentials into git repositories (by awslabs)
| trufflehog | git-secrets | |
|---|---|---|
| 31 | 35 | |
| 18,733 | 12,681 | |
| 2.8% | 0.4% | |
| 9.8 | 1.0 | |
| 4 days ago | about 1 year ago | |
| Go | Shell | |
| GNU Affero General Public License v3.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
trufflehog
Posts with mentions or reviews of trufflehog.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-07-25.
- TruffleHog: Find, verify, and analyze leaked credentials
-
Scan secret using trufflehog
Trufflehog is a tool that can scan multiple sources (filesystem, git, have a pre commit hook, Postman), integrate in CI / Docker environment, etc... .
-
Accident Forgiveness
https://github.com/trufflesecurity/trufflehog is a similar tool but checks for far more secrets, so I think it'd be a better choice.
-
Using TruffleHog and pre-commit hook to prevent secret exposure
Here for Linux and Windows users
-
Anyone Can Access Deleted and Private Repository Data on GitHub
It's probably either that they took the picture a while ago, or they were going character by character and accidentally screenshot with one too few.
https://github.com/trufflesecurity/trufflehog/commit/7bc0b2 https://github.com/trufflesecurity/trufflehog/commit/7bc0b4 https://github.com/trufflesecurity/trufflehog/commit/7bc0b8 https://github.com/trufflesecurity/trufflehog/commit/7bc0b8
-
Seeking help to identify vulnerabilities and secrets in a website backup file
Trufflehog
-
1 in 10 developers leaked an API-key in 2022
Frankly, I think it will take years to replace API-keys (if it will ever happen). Developers are much better-off using CLI tools that prevent leaking secrets by blocking commits to git (e.g., https://github.com/Infisical/infisical or https://github.com/trufflesecurity/trufflehog)
-
My boss keeps committing his creds into git
Trufflehog also offers pre-commit hooks. You can have it report on PRs too.
- Introducing DeepSecrets: a better appsec tool for secrets scanning
-
Nosey Parker: a new scanner to find misplaced secrets in textual data and Git history
Is this not just a another https://github.com/trufflesecurity/trufflehog?
git-secrets
Posts with mentions or reviews of git-secrets.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-03-17.
-
How To Push Your React JS Code To Your GitHub Repo
Q: What if I accidentally push sensitive information? A: If you push sensitive data, you should change your credentials immediately and consider using tools like git-secrets to help prevent this in the future.
-
How to Protect Only API Keys Instead of Entire Files on GitHub and From Its Commit History
Use tools like GitHub Dependabot or git-secrets to monitor your repositories for sensitive information.
- Prevents you from committing secrets and credentials into Git repositories
-
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
What are some alternatives?
When comparing trufflehog and git-secrets you can also consider the following projects:
talisman - Using a pre-commit hook, Talisman validates the outgoing changeset for things that look suspicious — such as tokens, passwords, and private keys.
gitleaks - Find secrets with Gitleaks 🔑
shhgit - Ah shhgit! Find secrets in your code. Secrets detection for your GitHub, GitLab and Bitbucket repositories.
secretlint - Pluggable linting tool to prevent committing credential.