A type-safe TypeScript SQL query builder
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 54%
Response Time: 6d
First Timer Success: 50%
kysely-org/kysely has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kysely-org/kysely respond to incoming external pull requests in approximately 147.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 53.5 places kysely-org/kysely in the B tier.
The external contributor pull request merge rate for kysely-org/kysely is 54.3%, based on public PR activity from non-core contributors.
kysely-org/kysely 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 kysely-org/kysely. 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/kysely-org/kysely?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~96 hours (68% approval). Large PRs (>500 lines) take ~708 hours (24% approval). Keep your diff compact for rapid review.
Hey 👋 The example application under /example is outdated in terms of stack and maybe even patterns/practices. Let's modernize it by updating the stack to reflect the flavors used nowadays in production full-stack applications. Also, ensure best practices are followed for auth, storage, Kysely usage, etc. Keep it simple, but production-like. Out of scope: cloud. It shouldn't be Vercel/Cloudflare/AWS Lambda ready. CI. remote database integration. any remote service integrations - it should be 100% local, "roll your own" everything. Bonus points: it reproduces the classic Northwind Traders application. end-to-end type-safety.
Hey 👋 Getting the following when starting or building the docs site: [WARNING] [docusaurus-plugin-llms-txt] WARNING: Excluded 13 routes by current config Could be a nothing burger. Let's make sure it's not or fix it.
Hey 👋 There's been some changes in how docs sites expose these since the last time we added llms-txt support. Let's ensure we are aligned with industry standards.
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 kysely-org/kysely, 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 kysely-org/kysely acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.3% were successfully merged into the primary branch.
kysely-org/kysely has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 53.5 places kysely-org/kysely in the Solid tier.
The external pull request merge rate is 54.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kysely-org/kysely 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 kysely-org/kysely 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.