runs anywhere. uses anything
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 72%
Response Time: -
First Timer Success: 42%
Gitlawb/openclaude has a recorded first-timer success rate of 41.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Gitlawb/openclaude 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 59.3 places Gitlawb/openclaude in the A tier.
The external contributor pull request merge rate for Gitlawb/openclaude is 72.0%, based on public PR activity from non-core contributors.
Gitlawb/openclaude does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Rigorous architecture standards (64% critical review signals). Ensure PRs strictly follow guidelines before requesting review in Gitlawb/openclaude.
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/openclaude?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (90% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
We have recently updated the contribution rules and expectations for the OpenClaude codebase. Two important documents are now available or have been substantially revised: AGENTS.md has been added. CONTRIBUTING.md has been significantly updated. Before preparing a pull request for an issue, bug fix, feature, or other change, please ensure that both you and any agent, harness, or automation you are using have reviewed these documents. These updates are intended to improve the quality and maintainability of contributions. In particular, we are placing more emphasis on: Avoiding duplicate pull requests. Reducing low-value or incomplete contributions. Ensuring timely follow-up on requested changes. Keeping pull requests aligned with the project’s current goals and direction. Pull requests that duplicate existing work, do not meaningfully improve the project, or remain inactive for extended periods may be closed without further notice. Repeated issues may also result in contributor wa
Hello everyone, we’re inviting you to contribute to and star one of our open-source repositories: Git Nodes. Git Nodes is the decentralized node backend for Gitlawb, built to become core infrastructure for the agentic future. We’re also inviting open-source contributors from OpenClaude to help build Git Nodes with us. Agents need decentralized git infrastructure. Let’s build it together. https://github.com/Gitlawb/node
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/openclaude, 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/openclaude acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.0% were successfully merged into the primary branch.
Gitlawb/openclaude has a recorded first-timer success rate of 41.5%. Repositories ranked Welcoming 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 59.3 places Gitlawb/openclaude in the Welcoming tier.
The external pull request merge rate is 72.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Gitlawb/openclaude 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/openclaude 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.