helm/chartmuseum

helm chart repository server

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 18th, 2026
Created on September 19th, 2017
Open Issues & Pull Requests: 119 (+0)
GitHub issues: Enabled
Number of forks: 407
Total Stargazers: 3,844 (+0)
Total Subscribers: 55 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.0 days
Mean response time: 146.8 days
90th percentile: 513.8 days
Tracked items: 29

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 962 days
Stale 30+ days: 7
Stale 90+ days: 7

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • dependencies (3)
  • proposal (2)
  • doc (1)
  • good first issue (1)
  • help wanted (1)
  • rc: next (1)

Most active issues this week

Detailed Description

ChartMuseum is a Helm chart repository server that enables hosting and serving Helm charts over HTTP.

ChartMuseum solves the problem of managing and distributing Helm charts within organizations by providing a dedicated repository server. It accepts chart uploads, stores them, and serves them to Kubernetes clusters and deployment tools that need to fetch charts. The server implements the Helm repository protocol, allowing standard Helm clients to discover and install charts from it without requiring external infrastructure like cloud storage or manual file management.

Teams should choose ChartMuseum when they need a self-hosted chart repository with straightforward deployment and management. It suits organizations that want to maintain charts internally, control access to their chart artifacts, or avoid dependency on public chart repositories. The tool is particularly valuable for teams building private charts or managing multiple chart versions across different environments.

The project maintains steady development activity with regular commits addressing bug fixes and feature improvements. The codebase receives ongoing attention to maintain compatibility with evolving Helm standards and Kubernetes practices. Development includes responsiveness to reported issues and incorporation of community contributions, indicating active stewardship of the project's stability and usability.