head to head · open source

gitleaks vs tork

gitleaks has 29,364 GitHub stars, 2,236 forks, 481 open issues and last shipped 9 days ago. tork has 817 stars, 63 forks, 20 open issues and last shipped 2 months ago. gitleaks leads on adoption by 3,494% (29,364 vs 817 stars). gitleaks is written in Go under MIT; tork is written in Go under MIT. gitleaks has attracted 8% as many forks as stars, tork 8%. gitleaks was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (go, golang), 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.

gitleaks ★ 29K tork ★ 817 category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

gitleaks tork
GitHub stars ★ 29K ★ 817
License MIT MIT
Written in Go Go
Last push 2026-09-09 2026-07-21
Forks ⑂ 2.2K ⑂ 63
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

full gitleaks profile →

pick tork if

  • You want the tork feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Go
  • You evaluated both and tork fits your workflow better

full tork profile →

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 tork

Tork is a lightweight, distributed workflow engine written in Go and released under the MIT license. It runs each task of a job as a script inside its own container, so work is defined in YAML rather than as compiled code. The project lives in the Go ecosystem and uses Docker, Podman, or a plain shell as its task runtime, with PostgreSQL as the datastore and a message broker such as RabbitMQ for distributed operation.

read the full tork overview →

More in Infrastructure & Operations

Immich ★ 114K Uptime Kuma ★ 91K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K

Related comparisons

compose vs gitleaks compose vs conductor compose vs xxl-job compose vs kestra compose vs haystack compose vs rancher conductor vs xxl-job compose vs prefect uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana uptime-kuma vs huginn worldmonitor vs huginn immich vs paperless-ngx immich vs ceph immich vs filestash immich vs garage immich vs storj immich vs alarik immich vs spinifex paperless-ngx vs ceph

More Orchestration & Scheduling projects

Compare either of these against the rest of the Orchestration & Scheduling field.

gitleaks vs compose gitleaks vs conductor gitleaks vs xxl-job gitleaks vs Kestra gitleaks vs haystack gitleaks vs rancher gitleaks vs Prefect gitleaks vs Archon gitleaks vs Temporal gitleaks vs rowboat gitleaks vs Trigger gitleaks vs dolphinscheduler

Frequently asked questions

Is gitleaks or tork more popular?

gitleaks has 29,364 GitHub stars and tork has 817. gitleaks has the larger community by that measure.

Are gitleaks and tork free?

Both are open source. gitleaks is licensed under MIT and tork under MIT. Neither carries a licence fee.

What is the difference between gitleaks and tork?

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

Choose gitleaks if you want the larger community (29,364 stars) or its MIT licence terms. Choose tork if its feature set, stack or MIT licence fits better. Both are self-hostable.