The Rancher UI
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 73%
Response Time: 1d
First Timer Success: 73%
rancher/dashboard has a recorded first-timer success rate of 72.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in rancher/dashboard respond to incoming external pull requests in approximately 28.2 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 65.9 places rancher/dashboard in the A tier.
The external contributor pull request merge rate for rancher/dashboard is 72.5%, based on public PR activity from non-core contributors.
rancher/dashboard currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in rancher/dashboard. Prompt code reviews with positive guidance for new contributors.
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/rancher/dashboard?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (91% approval). Large PRs (>500 lines) take ~135 hours (33% approval). Keep your diff compact for rapid review.
In version 2.13.1, user can enable/disable one Confirmation Setting in the Preference : scaling down node User should be able to enable/disable each confirmation setting : example : Redeploy, etc Alternative A : Make this available in the "Global settings / UI Performance Settings" Alternative B : User should be able to enable/disable all confirmation setting with one checbox (not separatly)
Starred section should always be open User adds his favorites item in this box, so please, let it always open. Suggestion : remove it from the accordion, put it in a single list up to the accordion : same color, same design : but opened Optionnal : Allow the user to fold/unfold it if needed Regards
When redeploying many deploiement, a popup ask for confirmation : great idea But the popup just mention the name of the deploiement, so as describe bellow it's not so usefull Please prefix the depl. name's with their namespace Also, please, make them in a list (ul / li) insteadof kilometer comma separated Regards
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 rancher/dashboard, 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 rancher/dashboard acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.5% were successfully merged into the primary branch.
rancher/dashboard has a recorded first-timer success rate of 72.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 65.9 places rancher/dashboard in the Welcoming tier.
The external pull request merge rate is 72.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, rancher/dashboard currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for rancher/dashboard 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.