High performance reactive SQL client written in Java
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 33%
Response Time: -
First Timer Success: -
eclipse-vertx/vertx-sql-client 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 eclipse-vertx/vertx-sql-client 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 52.7 places eclipse-vertx/vertx-sql-client in the B tier.
The external contributor pull request merge rate for eclipse-vertx/vertx-sql-client is 33.3%, based on public PR activity from non-core contributors.
eclipse-vertx/vertx-sql-client currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in eclipse-vertx/vertx-sql-client 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/eclipse-vertx/vertx-sql-client?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (42% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Describe the feature Transactional Event Queues (or TEQ for short) is a capability that provides Queuing mechanisms when working with an Oracle database. Over time it has evolved and now provides: Event publishing within a transaction (rollback => no publication), can participate to the business transaction (commit => both business data changes and message/event(s) publication in one ACID transaction) publish and subscribe (asynch notification) event propagation Kafka API compatibility real-time SQL over queues partitioning of queues for scalability ... Contribution No response
Describe the feature On a project, we are required to use access tokens to connect to the MSSQL databases instances. The project requires to not use user/password combinations for login because of audit requirements. Contribution I have a PR ready to implement this change for version 4.5.30, since that is the version internally used by Quarkus.
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 eclipse-vertx/vertx-sql-client, 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 eclipse-vertx/vertx-sql-client acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
eclipse-vertx/vertx-sql-client 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 52.7 places eclipse-vertx/vertx-sql-client in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eclipse-vertx/vertx-sql-client currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for eclipse-vertx/vertx-sql-client 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.