ChartMuseum

Self-hosted Helm chart repository server for publishing, storing, and distributing container charts, with support for local and cloud storage backends.

  • Development
  • Tools & Utilities
Self-hosted Helm chart repository server for publishing, storing, and distributing container charts, with support for local and cloud storage backends.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

67/100 Good

Maintained
84last commit 17 days ago
Popular
723,851 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
71no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 4.6/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
3,851
Open issues
121
Last commit
2026-11-04
Latest release
v0.16.6
License
Apache-2.0
Activity
rising

Checked 14 days ago - source: GitHub (helm/chartmuseum)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Pick where charts are stored Start with local storage by setting --storage local and --storage-local-rootdir to a folder you can back up, and choose a --port like 8080 for the web/API. If the folder or port is wrong, ChartMuseum starts but cannot save/find charts or you can't reach it. source
  • Set cloud storage details first If you use a cloud backend, fill in its storage name, bucket/container, region/endpoint, and any required keys before starting. Missing or mismatched settings make ChartMuseum fail to upload or list charts. source
  • Choose who can upload charts Add --basic-auth-user and --basic-auth-pass when uploads should need a login; add --auth-anonymous-get only if you want read-only access without credentials. Without a clear rule, public access may be either blocked or too open for your setup. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can Kubernetes clusters pull Helm charts from a private ChartMuseum?

Yes. The source describes storing built Helm charts in a private ChartMuseum instance and having Kubernetes clusters pull them during deployment.

Can I use Amazon S3 or Azure Blob Storage as ChartMuseum storage?

Yes. The source says ChartMuseum supports cloud storage backends, including Amazon S3 and Microsoft Azure Blob Storage.

Does ChartMuseum support JWT-based HTTP authorization?

The docs describe a chartmuseum/auth library for generating ChartMuseum JWT tokens and authorizing HTTP requests.

What upgrade approaches are discussed after the first Helm release?

The source contrasts changing the chart version, pushing to ChartMuseum, then running helm repo update and helm upgrade, with using helm upgrade --set and a local values file without changing the repository.

Answers sourced from chartmuseum.com, chartmuseum.com, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads