head to head · open source

gitleaks vs flowable-engine

gitleaks has 30,603 GitHub stars, 2,330 forks, 481 open issues and last shipped 6 days ago. flowable-engine has 9,633 stars, 2,902 forks, 411 open issues and last shipped 16 days ago. gitleaks leads on adoption by 218% (30,603 vs 9,633 stars). gitleaks is written in Go under MIT; flowable-engine is written in Java under Apache-2.0. gitleaks has attracted 8% as many forks as stars, flowable-engine 30%. gitleaks 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 flowable-engine ★ 9.6K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

gitleaks flowable-engine
GitHub stars ★ 31K ★ 9.6K
License MIT Apache-2.0
Written in Go Java
Last push 2026-10-28 2026-10-18
Forks ⑂ 2.3K ⑂ 2.9K
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 flowable-engine if

  • You want the flowable-engine feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches Java
  • You evaluated both and flowable-engine fits your workflow better

full flowable-engine 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 flowable-engine

Flowable ======== Homepage: flowable / flowəb(ə)l / a compact and highly efficient workflow and Business Process Management (BPM) platform for developers, system admins and business users. a lightning fast, tried and tested BPMN process engine, CMMN case engine and DMN rule engine written in Java. It is Apache 2.0 licensed open source, with a committed community. can run embedded in a Java application, or as a service on a server, a cluster, and in the cloud. It integrates perfectly with Spring. With a rich Java and REST API, it is the ideal engine for orchestrating human or system activities. Introduction…

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

gitleaks has 30,603 GitHub stars and flowable-engine has 9,633. gitleaks has the larger community by that measure.

Are gitleaks and flowable-engine free?

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

What is the difference between gitleaks and flowable-engine?

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

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