Automatically generate server and client framework code based on descriptive files (proto/api/sql), while using built-in jzero-skills to empower AI to generate production-ready business code adhering to best practices.
C-Rank Grade: B (Solid) - 38/100
External PR Merge Rate: 78%
Response Time: 1h
First Timer Success: -
jzero-io/jzero 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 jzero-io/jzero respond to incoming external pull requests in approximately 1.5 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 38.2 places jzero-io/jzero in the B tier.
The external contributor pull request merge rate for jzero-io/jzero is 78.4%, based on public PR activity from non-core contributors.
jzero-io/jzero currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Go project in jzero-io/jzero 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/jzero-io/jzero?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~7 hours (35% approval). Keep your diff compact for rapid review.
非常感谢每一位持续关注并使用 jzero 的朋友。我们会持续投入，尽力把 jzero 变得更好，努力让 jzero 社区更加繁荣。为了更好的聆听社区的声音，吸引更多的人使用和参与，我们期待您在此提交一条评论, 评论内容包括: 您可以参考下面的样例来提供您的信息： 项目：xx 地址：xx
非常感谢每一位持续关注并使用 jzero 的朋友。我们会持续投入，尽力把 jzero 变得更好，努力让 jzero 社区更加繁荣。为了更好的聆听社区的声音，吸引更多的人使用和参与，我们期待您在此提交一条评论, 评论内容包括: 您所在公司、学校或组织 官方网站 您可以参考下面的样例来提供您的信息： 公司：xx 网址：xx
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 jzero-io/jzero, 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 jzero-io/jzero acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.4% were successfully merged into the primary branch.
jzero-io/jzero 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 ~1 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 38.2 places jzero-io/jzero in the Solid tier.
The external pull request merge rate is 78.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jzero-io/jzero 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 jzero-io/jzero 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.