The Cluster API provider for creating microvm (i.e. Firecracker, Cloud Hypervisor) clusters
C-Rank Grade: B (Solid) - 45/100
External PR Merge Rate: 19%
Response Time: <1h
First Timer Success: -
liquidmetal-dev/cluster-api-provider-microvm has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in liquidmetal-dev/cluster-api-provider-microvm respond to incoming external pull requests in approximately 0.1 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 45.1 places liquidmetal-dev/cluster-api-provider-microvm in the B tier.
The external contributor pull request merge rate for liquidmetal-dev/cluster-api-provider-microvm is 18.8%, based on public PR activity from non-core contributors.
liquidmetal-dev/cluster-api-provider-microvm currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in liquidmetal-dev/cluster-api-provider-microvm 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/liquidmetal-dev/cluster-api-provider-microvm?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (23% approval). Large PRs (>500 lines) take ~0 hours (15% approval). Keep your diff compact for rapid review.
We need to update the provider to the v1beta2 contract before v1beta1 is dropped. Tasks: Adopt v1beta2 internally (and CAPI v1.11+) - CAPMVM types willl adhere to v1beta1 contract Do release Create v1alpha2 API version Add v1beta2 fields Mark old fields as deprecated Add metav1.Conditions Do release Ref: https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.10-to-v1.11#suggested-changes-for-providers
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 liquidmetal-dev/cluster-api-provider-microvm, 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 liquidmetal-dev/cluster-api-provider-microvm acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 18.8% were successfully merged into the primary branch.
liquidmetal-dev/cluster-api-provider-microvm has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 45.1 places liquidmetal-dev/cluster-api-provider-microvm in the Solid tier.
The external pull request merge rate is 18.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, liquidmetal-dev/cluster-api-provider-microvm 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 liquidmetal-dev/cluster-api-provider-microvm 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.