head to head · open source
gitleaks vs libfork
gitleaks has 30,603 GitHub stars, 2,330 forks, 481 open issues and last shipped 6 days ago. libfork has 901 stars, 46 forks, 10 open issues and last shipped 5 months ago. gitleaks leads on adoption by 3,297% (30,603 vs 901 stars). gitleaks is written in Go under MIT; libfork is written in C++ under MPL-2.0. gitleaks has attracted 8% as many forks as stars, libfork 5%. gitleaks was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| gitleaks | libfork | |
|---|---|---|
| GitHub stars | ★ 31K | ★ 901 |
| License | MIT | MPL-2.0 |
| Written in | Go | C++ |
| Last push | 2026-10-28 | 2026-05-25 |
| Forks | ⑂ 2.3K | ⑂ 46 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick gitleaks if
- You weight community size — 31K stars and counting
- You want the MIT license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick libfork if
- You want the libfork feature set and don't need the biggest community
- You prefer the MPL-2.0 license terms
- Your stack matches C++
- You evaluated both and libfork fits your workflow better
About gitleaks
Gitleaks [!WARNING] Gitleaks is feature complete. I'm not merging new features into Gitleaks. Future releases will be security patches only. I'm shifting my focus to Betterleaks [license]: ./LICENSE [badge license]: [go docs badge]: [go docs]: [badge build]: [build]: [go report card badge]: [go report card]: [dockerhub]: [dockerhub badge]: [gitleaks action]: [gitleaks badge]: [![GitHub Action Test][badge build]][build] [![Docker Hub][dockerhub badge]][dockerhub] [![Gitleaks Action][gitleaks badge]][gitleaks action] [![GoDoc][go docs badge]][go docs] [![GoReportCard][go report card badge]][go report card]…
read the full gitleaks overview →
About libfork
Welcome to libfork 🍴 A bleeding edge, lock free, wait free, continuation stealing coroutine tasking library. Now supplying 🌵! Libfork is primarily an abstraction for fully portable, strict, fork join parallelism. This is made possible without the use of any macros/inline assembly using C++20's coroutines. Ultra fine grained parallelism (the ability to spawn tasks with very low overhead) is enabled by an innovative implementation of an (almost) non allocating cactus stack utilizing segmented stacks . Libfork presents a cross platform API that decouples scheduling tasks (a customization point) from writing…
read the full libfork overview →
More in Infrastructure & Operations
Related comparisons
More Orchestration & Scheduling projects
Compare either of these against the rest of the Orchestration & Scheduling field.
Frequently asked questions
Is gitleaks or libfork more popular?
gitleaks has 30,603 GitHub stars and libfork has 901. gitleaks has the larger community by that measure.
Are gitleaks and libfork free?
Both are open source. gitleaks is licensed under MIT and libfork under MPL-2.0. Neither carries a licence fee.
What is the difference between gitleaks and libfork?
gitleaks is written in Go and libfork in C++. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, gitleaks or libfork?
Choose gitleaks if you want the larger community (30,603 stars) or its MIT licence terms. Choose libfork if its feature set, stack or MPL-2.0 licence fits better. Both are self-hostable.