I wrote Gitleaks, now I'm maintaining Betterleaks
zricethezav
13 points
3 comments
March 12, 2026
Related Discussions
Found 5 related stories in 55.0ms across 3,471 title embeddings via pgvector HNSW
- The Claude Code Source Leak: fake tools, frustration regexes, undercover mode alex000kim · 1057 pts · March 31, 2026 · 48% similar
- Dan rewrote chardet, relicensed to MIT. Original author broke 15-year silence sak84 · 11 pts · March 25, 2026 · 46% similar
- Claude Code full source code leaked on NPM dheerajmp · 47 pts · March 31, 2026 · 45% similar
- The Claude Code Leak mergesort · 79 pts · April 02, 2026 · 45% similar
- CLI RSS/Atom feed reader inspired by Taskwarrior, synced using Git todsacerdoti · 65 pts · March 08, 2026 · 45% 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