The coding agent that answers to you, your model, your machine, your rules.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 82%
Response Time: 10d
First Timer Success: 52%
Gitlawb/zero has a recorded first-timer success rate of 52.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Gitlawb/zero respond to incoming external pull requests in approximately 235.3 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 62.2 places Gitlawb/zero in the A tier.
The external contributor pull request merge rate for Gitlawb/zero is 82.0%, based on public PR activity from non-core contributors.
Gitlawb/zero does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in Gitlawb/zero. 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/Gitlawb/zero?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 Monday - Wednesday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~153 hours (96% approval). Large PRs (>500 lines) take ~1129 hours (37% approval). Keep your diff compact for rapid review.
On main at f30f550 there are four hand-rolled poll-until helpers in test code, each with its own deadline and interval and no shared implementation: internal/agent/async_diagnostics_test.go:126 waitForIdle 2s / 2ms internal/daemon/pool_test.go:245 waitFor 2s / 1ms internal/daemon/server_test.go:34 waitForFile 2s / 2ms internal/swarm/lifecycle_test.go:83 waitFor 3s / 5ms Found by the sweep for #1018, which also found that the tests that did NOT have one were the ones racing process startup on CI. A fifth copy is the likely outcome of the next such fix. Worth one shared helper in a small internal/testutil package: WaitFor(t, what string, cond func() bool) with a generous default deadline, a short interval, and a failure message that names what it was waiting for. The four sites migrate to it. Keep it simple; the value is one place to adjust when a deadline turns out too tight on a loaded runner, rather than four. Good first issu
deadcode -test ./... still reports a handful of genuinely-unreachable functions. This tracks removing them. Remaining after #706: five dead wrapper functions and unused test seams (plus five //go:build !linux stubs that are live on Linux and should stay).
Summary detectShellOutputIssue (internal/tools/shell_runtime.go:258) exists to turn "a Windows subsystem was denied under the sandbox's restricted token" into something the user can act on. It currently recognises two members of that family and not a third that looks likely. Being upfront about the evidence: I found this while triaging #788 and I have not reproduced a user hitting it. What I have verified is that the gap exists and that the failure would be opaque if it does occur. This issue is a request to confirm or dismiss, not a bug report with a repro attached. What the detector covers today Both existing cases follow the same pattern, a Windows security or service call failing under the restricted token, surfaced as a named shellIssue rather than a bare non-zero exit: msysRuntimeFailedInOutput covers MSYS/Cygwin startup denied (fatal error - CreateFileMapping, cygheap_user::init, win32 error 5 anchored to an MSYS marker). wslServiceDeniedInOutput covers the WSL launcher failing
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 Gitlawb/zero, 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 Gitlawb/zero acknowledge new external contributions in approximately 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.0% were successfully merged into the primary branch.
Gitlawb/zero has a recorded first-timer success rate of 52.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 62.2 places Gitlawb/zero in the Welcoming tier.
The external pull request merge rate is 82.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Gitlawb/zero does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for Gitlawb/zero 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.