Kubebuilder - SDK for building Kubernetes APIs using CRDs
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 72%
Response Time: 2d
First Timer Success: 74%
kubernetes-sigs/kubebuilder has a recorded first-timer success rate of 73.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubernetes-sigs/kubebuilder respond to incoming external pull requests in approximately 54.5 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 63.8 places kubernetes-sigs/kubebuilder in the A tier.
The external contributor pull request merge rate for kubernetes-sigs/kubebuilder is 71.5%, based on public PR activity from non-core contributors.
kubernetes-sigs/kubebuilder does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in kubernetes-sigs/kubebuilder. Maintains strict focus on technical quality and test standards.
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/kubernetes-sigs/kubebuilder?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~35 hours (89% approval). Large PRs (>500 lines) take ~262 hours (32% approval). Keep your diff compact for rapid review.
What is missing kubebuilder create webhook can add --defaulting or --programmatic-validation to a kind that already has a webhook. In that case it does not write a new file: WebhookUpdater (pkg/plugins/golang/v4/scaffolds/internal/templates/webhooks/webhook_updater.go) edits the existing one, which the user may already have filled in. The tests for that path only look at text: The Webhook Incremental Scaffolding specs in pkg/plugins/golang/v4/scaffolds/webhook_test.go read the generated file and search for strings. Every CLI call passes --make=false. The "should preserve customizations" spec even injects code that could never compile and still passes. The go/v4 E2E suite (test/e2e/v4) deploys and calls webhooks, but it always creates a webhook with all its options in one call. It never runs the update path. Nothing builds a project whose webhook was extended later, and nothing checks that the extended webhook is served. Why it matters The handler code lives in two places: the templat
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 kubernetes-sigs/kubebuilder, 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 kubernetes-sigs/kubebuilder acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.5% were successfully merged into the primary branch.
kubernetes-sigs/kubebuilder has a recorded first-timer success rate of 73.7%. 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 63.8 places kubernetes-sigs/kubebuilder in the Welcoming tier.
The external pull request merge rate is 71.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
kubernetes-sigs/kubebuilder does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for kubernetes-sigs/kubebuilder 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.