head to head · open source
gitleaks vs workflow-core
gitleaks has 29,396 GitHub stars, 2,236 forks, 481 open issues and last shipped 11 days ago. workflow-core has 5,926 stars, 1,262 forks, 133 open issues and last shipped 4 days ago. gitleaks leads on adoption by 396% (29,396 vs 5,926 stars). gitleaks is written in Go under MIT; workflow-core is written in C# under MIT. gitleaks has attracted 8% as many forks as stars, workflow-core 21%. workflow-core was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (hacktoberfest), so they are genuine substitutes rather than adjacent tools.
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 | workflow-core | |
|---|---|---|
| GitHub stars | ★ 29K | ★ 5.9K |
| License | MIT | MIT |
| Written in | Go | C# |
| Last push | 2026-09-09 | 2026-09-16 |
| Forks | ⑂ 2.2K | ⑂ 1.3K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick gitleaks if
- You weight community size — 29K stars and counting
- You want the MIT license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick workflow-core if
- You want the workflow-core feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches C#
- You evaluated both and workflow-core fits your workflow better
About gitleaks
Gitleaks is an MIT licensed, Go based command line tool that detects hardcoded secrets such as passwords, API keys, and tokens in git repositories, files, and standard input, and it serves developers and security teams that need to keep credentials out of source control.
read the full gitleaks overview →
About workflow-core
Workflow Core is a lightweight, embeddable workflow engine targeting .NET Standard, written in C and released under the MIT license. It lives in the .NET ecosystem, distributed as NuGet packages, and is built around the idea of long running processes that contain multiple tasks and must track their state between steps. Rather than running as a separate server, it is a library that is hosted inside an application, and it exposes a fluent C API for defining workflows. Workflows are expressed as a starting step followed by chained steps, and the same class can declare inputs and outputs that move data from one step …
read the full workflow-core 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 workflow-core more popular?
gitleaks has 29,396 GitHub stars and workflow-core has 5,926. gitleaks has the larger community by that measure.
Are gitleaks and workflow-core free?
Both are open source. gitleaks is licensed under MIT and workflow-core under MIT. Neither carries a licence fee.
What is the difference between gitleaks and workflow-core?
gitleaks is written in Go and workflow-core 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 workflow-core?
Choose gitleaks if you want the larger community (29,396 stars) or its MIT licence terms. Choose workflow-core if its feature set, stack or MIT licence fits better. Both are self-hostable.