head to head · open source
gitleaks vs workflow-core
gitleaks has 30,603 GitHub stars, 2,330 forks, 481 open issues and last shipped 6 days ago. workflow-core has 5,939 stars, 1,261 forks, 133 open issues and last shipped 4 days ago. gitleaks leads on adoption by 415% (30,603 vs 5,939 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 | ★ 31K | ★ 5.9K |
| License | MIT | MIT |
| Written in | Go | C# |
| Last push | 2026-10-28 | 2026-10-30 |
| Forks | ⑂ 2.3K | ⑂ 1.3K |
| 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 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 [!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 workflow-core
Workflow Core Workflow Core is a light weight embeddable workflow engine targeting .NET Standard. Think: long running processes with multiple tasks that need to track state. It supports pluggable persistence and concurrency providers to allow for multi node clusters. Announcements New related project: Conductor Conductor is a stand alone workflow server as opposed to a library that uses Workflow Core internally. It exposes an API that allows you to store workflow definitions, track running workflows, manage events and define custom steps and scripts for usage in your workflows. Documentation See Tutorial here…
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 30,603 GitHub stars and workflow-core has 5,939. 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 (30,603 stars) or its MIT licence terms. Choose workflow-core if its feature set, stack or MIT licence fits better. Both are self-hostable.