head to head · open source
gitleaks vs chart-releaser-action
gitleaks has 30,603 GitHub stars, 2,330 forks, 481 open issues and last shipped 6 days ago. chart-releaser-action has 667 stars, 222 forks, 79 open issues and last shipped 2 days ago. gitleaks leads on adoption by 4,488% (30,603 vs 667 stars). gitleaks is written in Go under MIT; chart-releaser-action is written in Shell under Apache-2.0. gitleaks has attracted 8% as many forks as stars, chart-releaser-action 33%. chart-releaser-action was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (ci-cd), 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 | chart-releaser-action | |
|---|---|---|
| GitHub stars | ★ 31K | ★ 667 |
| License | MIT | Apache-2.0 |
| Written in | Go | Shell |
| Last push | 2026-10-28 | 2026-11-01 |
| Forks | ⑂ 2.3K | ⑂ 222 |
| 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 chart-releaser-action if
- You want the chart-releaser-action feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Shell
- You evaluated both and chart-releaser-action 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 chart-releaser-action
chart releaser Action A GitHub action to turn a GitHub project into a self hosted Helm chart repo, using helm/chart releaser CLI tool. Usage Pre requisites 1. A GitHub repo containing a directory with your Helm charts (default is a folder named /charts , if you want to maintain your charts in a different directory, you must include a charts dir input in the workflow). 1. A GitHub branch called gh pages to store the published charts. 1. In your repo, go to Settings/Pages. Change the Source Branch to gh pages . 1. Create a workflow .yml file in your .github/workflows directory. An example workflow is available…
read the full chart-releaser-action 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 chart-releaser-action more popular?
gitleaks has 30,603 GitHub stars and chart-releaser-action has 667. gitleaks has the larger community by that measure.
Are gitleaks and chart-releaser-action free?
Both are open source. gitleaks is licensed under MIT and chart-releaser-action under Apache-2.0. Neither carries a licence fee.
What is the difference between gitleaks and chart-releaser-action?
gitleaks is written in Go and chart-releaser-action in Shell. 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 chart-releaser-action?
Choose gitleaks if you want the larger community (30,603 stars) or its MIT licence terms. Choose chart-releaser-action if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.