helm/helm
The Kubernetes Package Manager observed · 2026-08-28
Health v2 · maintenance only
99/100
- Activity 99
- Release rhythm 98
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 13.0
- age_days: 3985
- days_rel: 19
- days_push: 8
- n_releases_24m: 45
Adoption not part of the score
30178 stars · 7765 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Helm is the de facto package manager for Kubernetes, packaging pre-configured Kubernetes resources into versioned units called charts that can be installed, upgraded, and rolled back as single releases. It is a mature CNCF-graduated project written in Go, with a CLI client, a Go SDK, a plugin system (including WebAssembly-based plugins in v4), and support for distributing charts via traditional repositories and OCI registries.
Use cases
- install applications on kubernetes from packaged charts
- package my own kubernetes app as a reusable chart
- upgrade and roll back kubernetes releases safely
- deploy the same app to dev staging and prod with different values
- manage kubernetes yaml manifests without copy-paste
- share helm charts with my team or the community
- install charts from an oci container registry
When to choose
- you deploy or operate applications on Kubernetes and want repeatable, versioned installs
- you need per-environment configuration of Kubernetes manifests via values files
- you want to distribute your Kubernetes application as an installable package
- you need safe in-place upgrades and rollbacks of cluster releases
- you want to consume off-the-shelf software (databases, ingress controllers, monitoring stacks) from Artifact Hub or OCI registries
When to avoid
- you are not using Kubernetes - Helm charts only describe Kubernetes resources
- you prefer plain manifests with tools like kustomize for simple overlay-style customization
- you need a fully GitOps-declarative workflow without a CLI-driven release model (consider Flux or Argo CD, which can still use Helm charts)
- you depend on Helm v2 - it is long end-of-life and unsupported
Facets
cli-tool · maturity stable
package-manager deployment cli templating configuration-management ci-cd cloud-computing developer-tools self-hosted windows cli cloud cross-platform kubernetes helm-charts package-manager cncf go oci-registry release-management rollbacks containers devops linux macos docker
10 sources
- readme: https://github.com/helm/helm · fetched 2026-08-28 · 9f0e055e384f
- homepage: https://helm.sh · fetched 2026-08-29 · 3015608ac0c2
- site_page: https://helm.sh/docs/overview · fetched 2026-08-29 · 189c54b91e15
- site_page: https://helm.sh/docs · fetched 2026-08-29 · 151b8b0b772c
- site_page: https://helm.sh/docs/v3 · fetched 2026-08-29 · 59fae39f9dbc
- site_page: https://helm.sh/docs/v2 · fetched 2026-08-29 · 89e52bf83bc4
- site_page: https://helm.sh/docs/topics/architecture · fetched 2026-08-29 · 1e798b10499c
- site_page: https://helm.sh/docs/intro/quickstart · fetched 2026-08-29 · 42d5bf6fe41d
- site_page: https://helm.sh/docs/intro/install · fetched 2026-08-29 · 09eed50c47ed
- site_page: https://helm.sh/docs/intro/using_helm · fetched 2026-08-29 · 07ce49efee0a
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| helm/helm | main | 99 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem