🐶 Kubernetes CLI To Manage Your Clusters In Style!
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 38%
Response Time: 2d
First Timer Success: 30%
derailed/k9s has a recorded first-timer success rate of 30.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in derailed/k9s respond to incoming external pull requests in approximately 58.9 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 55.9 places derailed/k9s in the A tier.
The external contributor pull request merge rate for derailed/k9s is 37.8%, based on public PR activity from non-core contributors.
derailed/k9s currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in derailed/k9s.
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/derailed/k9s?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~38 hours (47% approval). Large PRs (>500 lines) take ~283 hours (17% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. Not really. Describe the solution you'd like Please add an option to select all items in the current working window. For example, after filtering resources, would be really handy to use "Ctrl+A" for deletion/scaling/restart/cordon/edit, etc. on the whole output. Describe alternatives you've considered At least an option to delete all pods in the output. Additional context
Is your feature request related to a problem? Please describe. When changing the view, it is not clear if there are no resources or if they have yet to be loaded. This is especially an issue in the Secrets view because secrets are loaded very slowly for some reason. Describe the solution you'd like A spinner with a message would be useful.
Is your feature request related to a problem? Please describe. When using t to transfer a file from a pod onto my local machine, my understanding is that the file always lands by default in the working directory I was in when I started k9s. I'd like to have a bit more control over where transferred files land on my local machine. Describe the solution you'd like I'd like a configuration setting that allows users to define a default directory for transferred files to land in. I'm open to either the directory being pre-populated in the file transfer dialog box (like the pod currently is), or for the directory to be "hidden" in that dialog box with the user understanding that the "To" field will be appended to the configuration setting directory. Describe alternatives you've considered I haven't considered many alternatives. The obvious alternative is just to type in the full destination path, but that's a bit tedious, which is why I'm looking for a solution. I'm very open to other, bette
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 derailed/k9s, 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 derailed/k9s acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 37.8% were successfully merged into the primary branch.
derailed/k9s has a recorded first-timer success rate of 30.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 55.9 places derailed/k9s in the Welcoming tier.
The external pull request merge rate is 37.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, derailed/k9s 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 derailed/k9s 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.