A CLI and package manager for building, distributing, and bootstrapping multi-cluster Kubernetes platforms via pure GitOps.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 85%
Response Time: 15h
First Timer Success: 67%
kubara-io/kubara has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubara-io/kubara respond to incoming external pull requests in approximately 15.4 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 66.7 places kubara-io/kubara in the A tier.
The external contributor pull request merge rate for kubara-io/kubara is 85.0%, based on public PR activity from non-core contributors.
kubara-io/kubara currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in kubara-io/kubara. 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/kubara-io/kubara?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 ~10 hours (96% approval). Large PRs (>500 lines) take ~74 hours (38% approval). Keep your diff compact for rapid review.
kubara init allows selecting general catalogs with --catalog. It would be useful to also select the bootstrap catalog explicitly, so both catalog types can be overridden in one command. For example: kubara init \ --bootstrap-catalog ./bootstrap \ --catalog ./general \ --catalog-overwrite The generated configuration should reference the selected bootstrap and general catalogs. Contributions are welcome — feel free to pick this up.
📝 Question While secrets are briefly mentioned in the prerequisites, I couldn't find any reference to them during the bootstrapping process. When using a SecretStore (e.g., OpenBao), secrets still need to be provisioned for components like ArgoCD or Grafana. However, this step is no longer mentioned later in the tutorial. 💡 What Have You Tried? The core problem is also described here: #301 I suggest updating the tutorial to include explicit instructions on how to configure and deploy these secrets during the bootstrapping phase. 📎 Additional Context / Logs No response ✅ Checklist I have searched existing issues I have checked the documentation
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 kubara-io/kubara, 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 kubara-io/kubara acknowledge new external contributions in approximately 15 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.0% were successfully merged into the primary branch.
kubara-io/kubara has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~15 hours. 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 66.7 places kubara-io/kubara in the Welcoming tier.
The external pull request merge rate is 85.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kubara-io/kubara 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 kubara-io/kubara 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.