The Helm website for docs, blog and project info.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 74%
Response Time: 4h
First Timer Success: 75%
helm/helm-www has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in helm/helm-www respond to incoming external pull requests in approximately 3.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 59.9 places helm/helm-www in the A tier.
The external contributor pull request merge rate for helm/helm-www is 73.9%, based on public PR activity from non-core contributors.
helm/helm-www currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in helm/helm-www welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/helm/helm-www?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (92% approval). Large PRs (>500 lines) take ~18 hours (33% approval). Keep your diff compact for rapid review.
The English cheat sheet at docs/intro/CheatSheet.mdx has a few entries that are out of date for Helm 4, plus some small mistakes. These came up while reviewing the French translation in #2260, which already fixes several of them. What needs to change Remove helm list --all. Helm 4 no longer has this flag. Plain helm list now shows releases in every status (see pkg/cmd/list.go in helm v4.3.0). Update the helm list description. It should say that by default it lists releases in any status. Update the helm list --deployed description. Remove "If no other is specified, this will be automatically enabled", which is no longer true. It should just say that it shows only deployed releases. Replace --dry-run with --dry-run=client in helm install <name> <chart> --dry-run --debug. A bare --dry-run is deprecated in Helm 4 and prints --dry-run is deprecated and should be replaced with '--dry-run=client'. Also drop the stray (p) from that line's comment. Add the missing argument to --values: helm u
While adding anchor IDs in PR #2216, i18n/fr/docusaurus-plugin-content-docs/version-3/chart_template_guide/function_list.md had all 18 section headings and all 18 table-of-contents entries changed from French to English. For example: -## Fonctions de chaînes de caractères +## String Functions {#string-functions} -* [Chaînes de caractères](#fonctions-de-chaînes-de-caractères) +* [String](#string-functions) The page body remains French, so the page now reads as English headings and English TOC over French prose. Why this isn't required The anchor convention only pins the ID, not the heading text. From community/localization.md: Add anchor IDs to any headings using the format ## Example Heading {#example-anchor-id}. The anchor IDs must be English language and match the anchor IDs of the corresponding heading in the English doc page. For example, ## 后端存储 {#storage-backends} matches ## Storage backends {#storage-backends}. The other four files touched in the same PR do exact
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to helm/helm-www, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of helm/helm-www acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.9% were successfully merged into the primary branch.
helm/helm-www has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 59.9 places helm/helm-www in the Welcoming tier.
The external pull request merge rate is 73.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, helm/helm-www currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for helm/helm-www are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.