tartufo
deadshot
tartufo | deadshot | |
---|---|---|
6 | 2 | |
484 | 190 | |
4.4% | 0.0% | |
6.0 | 0.0 | |
16 days ago | 6 days ago | |
Python | Python | |
GNU General Public License v3.0 only | 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.
tartufo
- Tartufo searches through Git repositories for high entropy strings and secrets
- Show HN: Tartufo, the godaddy Git secrets linter
- GitHub Access Token Exposure
-
Toyota Accidently Exposed a Secret Key Publicly on GitHub for Five Years
You could set up something like https://github.com/godaddy/tartufo in a pre-commit hook. Not sure if github has a way to hook into the push hooks on server side, they might though.
- Tartufo – effective finds secrets accidentally committed
deadshot
- Deadshot is a Pull Request scanner that looks for the introduction of secrets via PRs by matching each diff line against a set of known secret expressions.
-
Deadshot: Keep Sensitive Data Out of Code
Code is no place for credentials, secrets, SQL statements, or any kind of sensitive data. But everyone makes mistakes, and it's important to be able to catch human errors before they create real problems. It is impossible to manually monitor any organization's entire code base hoping to catch sensitive changes before they escape to live forever on Github. This is a problem every security team faces when dealing with product code. The Product Security team at Twilio needed an automated way to ensure that developers weren't accidentally adding sensitive data to code repositories and to flag sensitive changes for a security review. We knew we couldn't monitor all code manually. Our solution: an automated way to monitor GitHub repositories in real-time, catching any sensitive data at the pull request stage, flagging issues as well as changes to sensitive functionality for a manual review. Thus was born Deadshot – which we're happy to be releasing as open source today.
What are some alternatives?
leaky-repo - Benchmarking repo for secrets scanning
whispers - Identify hardcoded secrets in static structured text
ssh-crypt - This tool helps you to keep passwords inside your shell scripts safely
secrets - A command-line tool to prevent committing secret keys into your source code [Moved to: https://github.com/sirwart/ripsecrets]
Pathfinder - Search Strategy analysis and more for spatial navigation data in rodents
git-pull-request - Send git pull requests via command line
kscp - Kubernetes Secrets Control Plane
git-alerts - Tool to detect and monitor GitHub org users' public repositories for secrets and sensitive files
gitleaks - Protect and discover secrets using Gitleaks 🔑
github-peek - open a remote repo locally quickly [Moved to: https://github.com/rahulunair/repo-peek]