Apache Kyuubi is a distributed and multi-tenant gateway to provide serverless SQL on data warehouses and lakehouses.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 1%
Response Time: -
First Timer Success: -
apache/kyuubi 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 apache/kyuubi respond to incoming external pull requests in approximately 0.0 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 49.3 places apache/kyuubi in the B tier.
The external contributor pull request merge rate for apache/kyuubi is 0.5%, based on public PR activity from non-core contributors.
apache/kyuubi 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 apache/kyuubi. 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/apache/kyuubi?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 ~16 hours (1% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Code of Conduct I agree to follow this project's Code of Conduct Search before asking I have searched in the issues and found no similar issues. What type of changes will we make to the documentation? Showcase Affects Version(s) master,1.11.1 Improving the documentation TL;DR — Spark 4 compile support landed in #7256 (v1.10.3 / v1.11.x), but no Spark-4 artifact is published to Maven Central (https://mvnrepository.com/artifact/org.apache.kyuubi/kyuubi-spark-authz). Requesting it be added to the release matrix. Use case We run Spark 4.0 with Ranger-based authz. v1.11.1 builds cleanly from source against Spark 4.0 / Scala 2.13 / Java 21 using -Pspark-4.0, so we're currently building and hosting the jar on an internal repo. A published artifact on Central would let us — and other Spark 4 users — consume it directly. Ask Add a Spark 4 variant of kyuubi-spark-authz to the release matrix so future releases publish it to Maven Central. Happy to open a PR if a committer can point me
Code of Conduct I agree to follow this project's Code of Conduct Search before asking I have searched in the issues and found no similar issues. What type of changes will we make to the documentation? Refactoring Affects Version(s) master/1.11 Improving the documentation Description Currently, the Apache Kyuubi documentation uses a hybrid approach, mixing reStructuredText (.rst) and Markdown (.md) files, while being processed by Sphinx. While this hybrid approach provides flexibility (using myst-parser for Markdown), it introduces several challenges: Contributors need to be familiar with both syntaxes. Cross-referencing between RST and MD files can be error-prone and hard to detect. The build pipeline relies on multiple Sphinx extensions (like myst-parser, sphinx-markdown-tables) to bridge the gap. Formatting features available in RST might not be easily replicable in Markdown (or vice-versa). I propose migrating to a single technology to streamline the contribution process and
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 apache/kyuubi, 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 apache/kyuubi acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.5% were successfully merged into the primary branch.
apache/kyuubi 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 ~-. 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 49.3 places apache/kyuubi in the Solid tier.
The external pull request merge rate is 0.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/kyuubi 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 apache/kyuubi 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.