KubeFleet is an open-source Kubernetes multi-cluster application management solution.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 60%
Response Time: 4d
First Timer Success: 70%
kubefleet-dev/kubefleet has a recorded first-timer success rate of 70.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubefleet-dev/kubefleet respond to incoming external pull requests in approximately 94.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 60.0 places kubefleet-dev/kubefleet in the A tier.
The external contributor pull request merge rate for kubefleet-dev/kubefleet is 59.8%, based on public PR activity from non-core contributors.
kubefleet-dev/kubefleet currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in kubefleet-dev/kubefleet. Reviews pull requests with focus on project architectural goals.
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/kubefleet-dev/kubefleet?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~61 hours (75% approval). Large PRs (>500 lines) take ~452 hours (27% approval). Keep your diff compact for rapid review.
Election is using: "136224848560.hub.fleet.azure.com" see: kubefleet/cmd/hubagent/main.go Line 146 in e5f16f2 LeaderElectionID: "136224848560.hub.fleet.azure.com", This doesn't reflect the kubefleet project naming and product specific. Recommend changing to hub.kubefleet.io after assessing impact.
Describe the bug In pkg/scheduler/scheduler.go:189-197 (on main), the call site for s.lookupLatestPolicySnapshot calls s.queue.Forget(placementKey); return for any error. The helper currently returns three error categories: "no latest policy snapshot" — transient, plain fmt.Errorf "multiple active policy snapshots" — wrapped ErrUnexpectedBehavior List failure — ErrAPIServerError (and ErrUnexpectedBehavior for non-StatusError cache faults) All three take the same Forget-without-requeue path. The "no snapshot" case is recoverable via the policy-snapshot watcher (it fires on Create / IsLatestSnapshot flip). But for ErrAPIServerError (transient apiserver/cache blip during List) the placement is dropped from the queue with no requeue scheduled, and only re-enters via unrelated event sources (placement update, member-cluster churn, binding deletion). In a quiet cluster the failure window is effectively unbounded — the user sees SchedulingPolicyApplied=False with no progress until s
Summary There is a // TODO: should update scheduled bindings to the latest snapshot when it is updated to bound state. at pkg/controllers/rollout/controller_integration_test.go:1074. The existing integration test at that location verifies that bindings are not rolled out after the rollout strategy is changed to External. However, there is no integration test that verifies scheduled bindings pick up the latest resource snapshot (not the one they were originally scheduled with) when they transition to the Bound state during a rolling update. What to test When a new master resource snapshot is created while scheduled bindings exist: The rollout controller should transition scheduled bindings to Bound state The bound bindings should reference the latest resource snapshot, not the snapshot they were originally scheduled with This is the integration-test counterpart to the unit tests in TestPickBindingsToRoll (e.g., "test scheduled binding to bound, outdated resources and nil overrides - r
Summary There is a // TODO: add more tests at pkg/controllers/rollout/controller_test.go:1238 in TestPickBindingsToRoll. The existing 33 test cases cover the main happy paths but leave several code paths in pickBindingsToRoll and determineBindingsToUpdate untested. Missing Test Coverage Scheduled → Bound transition gaps Scheduled binding with latest resources (same snapshot, no overrides) — all current tests use outdated resources Scheduled binding with PickFixed placement type — only PickAll and PickN are tested Multiple scheduled bindings constrained by MaxSurge=0 — rollout should be blocked Scheduled + ready bound mix with MaxSurge constraining partial rollout Multiple scheduled bindings with percentage-based MaxSurge (rounding behavior) Untested code paths in pickBindingsToRoll IsBindingDiffReported path (lines ~400, ~449) — no test creates a binding where IsBindingDiffReported() returns true, affecting canBeReadyBindings membership Scheduled binding with DeletionTimes
What actuals_test.go currently skips annotation comparison when the previous state is known. Tighten assertions to compare annotations where the test has enough context to do so. Location test/scheduler/actuals_test.go:289
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 kubefleet-dev/kubefleet, 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 kubefleet-dev/kubefleet acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 59.8% were successfully merged into the primary branch.
kubefleet-dev/kubefleet has a recorded first-timer success rate of 70.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 60.0 places kubefleet-dev/kubefleet in the Welcoming tier.
The external pull request merge rate is 59.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kubefleet-dev/kubefleet currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kubefleet-dev/kubefleet 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.