Visualize and share your data. All in SQL. Powered by DuckDB.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 87%
Response Time: 17d
First Timer Success: 50%
taleshape-com/shaper has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in taleshape-com/shaper respond to incoming external pull requests in approximately 408.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 56.7 places taleshape-com/shaper in the A tier.
The external contributor pull request merge rate for taleshape-com/shaper is 87.1%, based on public PR activity from non-core contributors.
taleshape-com/shaper currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in taleshape-com/shaper. Prompt code reviews with positive guidance for new contributors.
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/taleshape-com/shaper?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~265 hours (96% approval). Large PRs (>500 lines) take ~1959 hours (39% approval). Keep your diff compact for rapid review.
It would be nice if the min and max values of a line chart’s y‑axis could be customized, instead of always starting at zero, as seems to be the case at the moment. This would avoid curves that look too compressed or overly smoothed. Thanks in advance.
We have a mechanism to limit queries to 3k rows. But this currently only limits how much is returned to the client. Internally the go-duckdb driver still loads the whole result into memory. That means with big queries you can actually kill the server by running out of memory. Unfortunately this is not something Shaper can fix. There actually is a DuckDB C API to stream results. But go-duckdb doesn't use that. So to fix this in Shaper someone needs to refactor go-duckdb to use the streaming API internally instead of loading all results into memory.
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 taleshape-com/shaper, 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 taleshape-com/shaper acknowledge new external contributions in approximately 17 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.1% were successfully merged into the primary branch.
taleshape-com/shaper has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 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 56.7 places taleshape-com/shaper in the Welcoming tier.
The external pull request merge rate is 87.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, taleshape-com/shaper 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 taleshape-com/shaper 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.