head to head · open source

gitleaks vs workflow

gitleaks has 30,603 GitHub stars, 2,330 forks, 481 open issues and last shipped 6 days ago. workflow has 2,487 stars, 387 forks, 360 open issues and last shipped yesterday. gitleaks leads on adoption by 1,131% (30,603 vs 2,487 stars). gitleaks is written in Go under MIT; workflow is written in TypeScript under Apache-2.0. gitleaks has attracted 8% as many forks as stars, workflow 16%. workflow 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.

gitleaks ★ 31K workflow ★ 2.5K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

gitleaks workflow
GitHub stars ★ 31K ★ 2.5K
License MIT Apache-2.0
Written in Go TypeScript
Last push 2026-10-28 2026-11-02
Forks ⑂ 2.3K ⑂ 387
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

full gitleaks profile →

pick workflow if

  • You want the workflow 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 workflow fits your workflow better

full workflow profile →

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

Workflow SDK Workflow SDK makes TypeScript and JavaScript functions durable. It persists workflow progress, retries failed steps, and provides built in observability. Workflows can suspend without using compute while they wait. Quick start Install the SDK in an existing project: Configure the integration for your framework. For example, with Next.js: Then start a workflow from an API route, Server Action, or other server side code: Run your app, then open the local observability UI in another terminal: Choose your framework in the getting started guides. [!NOTE] The workflow package includes its full…

read the full workflow 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 more popular?

gitleaks has 30,603 GitHub stars and workflow has 2,487. gitleaks has the larger community by that measure.

Are gitleaks and workflow free?

Both are open source. gitleaks is licensed under MIT and workflow under Apache-2.0. Neither carries a licence fee.

What is the difference between gitleaks and workflow?

gitleaks is written in Go and workflow 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 workflow?

Choose gitleaks if you want the larger community (30,603 stars) or its MIT licence terms. Choose workflow if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.