Long-horizon agent control plane for durable, governed work across Codex, Claude Code, and other harnesses.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 93%
Response Time: 17h
First Timer Success: 58%
huangruiteng/loopx has a recorded first-timer success rate of 58.1%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in huangruiteng/loopx respond to incoming external pull requests in approximately 16.6 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 74.4 places huangruiteng/loopx in the S tier.
The external contributor pull request merge rate for huangruiteng/loopx is 92.7%, based on public PR activity from non-core contributors.
huangruiteng/loopx does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in huangruiteng/loopx. Ensure PR scope matches issue requirements closely before requesting review.
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/huangruiteng/loopx?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (96% approval). Large PRs (>500 lines) take ~80 hours (42% approval). Keep your diff compact for rapid review.
Summary / 目标 Help build a capable LoopX manager that can investigate with ordinary host tools, hand work to another agent without losing its meaning, and return the result automatically. The bilingual RFC landed in #4330. This is an implementation invitation, not a feature-release announcement: the document records proposed behavior and acceptance requirements, not completed M1–M4 qualification. RFC: English · 中文 Scenarios and design feedback: Discussion #4340 / 场景与方案讨论. Direction: Operator Surface / IM Integration, with a shared TypeScript collaboration boundary. Intended base: current main; check existing work before choosing a slice. This issue is a public coordination entry point. Link existing engineering Todos, issues and PRs; do not create a parallel authoritative task ledger. Contribution areas Area Useful contribution Acceptance anchors / dependencies M1 — capable host manager Ordinary file/Git/tool investigation within existing authorizatio
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 huangruiteng/loopx, 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 huangruiteng/loopx acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.7% were successfully merged into the primary branch.
huangruiteng/loopx has a recorded first-timer success rate of 58.1%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 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 74.4 places huangruiteng/loopx in the Elite tier.
The external pull request merge rate is 92.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
huangruiteng/loopx 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 huangruiteng/loopx 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.