I wrote Gitleaks, now I'm maintaining Betterleaks
zricethezav
13 points
3 comments
March 12, 2026
Related Discussions
Found 5 related stories in 1028.2ms across 14,015 title embeddings via pgvector HNSW
- Lovable leaks source code, secrets, chats for projects created before Nov 2025 Tiberium · 14 pts · April 20, 2026 · 50% similar
- The Claude Code Source Leak: fake tools, frustration regexes, undercover mode alex000kim · 1057 pts · March 31, 2026 · 48% similar
- GitHub Alternatives? krthr · 11 pts · April 27, 2026 · 48% similar
- Lessons Learned from CISA's Recent GitHub Leak Bender · 14 pts · July 13, 2026 · 47% similar
- Hacker News but for independent blogs headalgorithm · 565 pts · June 17, 2026 · 47% similar
Discussion Highlights (3 comments)
zricethezav
8 years ago I wrote the first lines of Gitleaks and have been hooked on finding leaked secrets since. Gitleaks grew from a small project to a name recognized by developers and security folks. It sucks but I gotta take a step back from the project. I'll cut security releases but don't expect any new features from me. But I'm not stepping back from secrets scanning! I'm working full time on maintaining Betterleaks, a drop-in replacement for Gitleaks with some fun new features and improvements like rule-defined validation, faster scans, new filters like token efficiency, and more. Happy to chat about it and sorry if this causes any migration headache `alias gitleaks='betterleaks'` should do the trick
missionhq1
are you looking for new maintainers?
singulasar
https://github.com/betterleaks/betterleaks