head to head · open source
gitleaks vs openworkflow
gitleaks has 30,603 GitHub stars, 2,330 forks, 481 open issues and last shipped 6 days ago. openworkflow has 1,346 stars, 73 forks, 12 open issues and last shipped 4 days ago. gitleaks leads on adoption by 2,174% (30,603 vs 1,346 stars). gitleaks is written in Go under MIT; openworkflow is written in TypeScript under Apache-2.0. gitleaks has attracted 8% as many forks as stars, openworkflow 5%. openworkflow 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 | openworkflow | |
|---|---|---|
| GitHub stars | ★ 31K | ★ 1.3K |
| License | MIT | Apache-2.0 |
| Written in | Go | TypeScript |
| Last push | 2026-10-28 | 2026-10-30 |
| Forks | ⑂ 2.3K | ⑂ 73 |
| 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 openworkflow if
- You want the openworkflow feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches TypeScript
- You evaluated both and openworkflow 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 openworkflow
OpenWorkflow OpenWorkflow is a TypeScript framework for building durable, resumable workflows that can pause for seconds or months, survive crashes and deploys, and resume exactly where they left off all without extra servers to manage. Quick Start The CLI will guide you through setup and generate everything you need to get started. Documentation Documentation Quick Start Guide Core Concepts Advanced Patterns Production Checklist OpenTelemetry Architecture Read ARCHITECTURE.md for a deep dive into how OpenWorkflow works under the hood. Examples Check out examples/ for working examples. Contributing We welcome…
read the full openworkflow 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 openworkflow more popular?
gitleaks has 30,603 GitHub stars and openworkflow has 1,346. gitleaks has the larger community by that measure.
Are gitleaks and openworkflow free?
Both are open source. gitleaks is licensed under MIT and openworkflow under Apache-2.0. Neither carries a licence fee.
What is the difference between gitleaks and openworkflow?
gitleaks is written in Go and openworkflow in TypeScript. 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 openworkflow?
Choose gitleaks if you want the larger community (30,603 stars) or its MIT licence terms. Choose openworkflow if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.