A control plane with a durable state kernel for long-horizon agents and teams. Keep work moving and improving across sessions, with less human attention.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 14%
Response Time: -
First Timer Success: 20%
loopx-project/loopx has a recorded first-timer success rate of 20.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in loopx-project/loopx 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 68.0 places loopx-project/loopx in the A tier.
The external contributor pull request merge rate for loopx-project/loopx is 14.3%, based on public PR activity from non-core contributors.
loopx-project/loopx currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in loopx-project/loopx. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in loopx-project/loopx focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/loopx-project/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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (18% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Outcome / 目标 完成研究探索控制面的证据、组合与闭环契约。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree. Canonical design: RFC. Roadmap: S3/S8/S11, under #4574. Design acceptance is distinct from implementation, live qualification and promotion. Current boundary Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim. #3173 shipped explicit composition projection and successor binding. The RFC keeps canonical research observation/closure, shared write-time enforcement and model-selection qualification separate; deferred inference is not current behavior. Work remaining Reconcile M1/M2 against current Explore owners, then complete explicit-only evidence, closure and composition-gap projection with actual consumers. Implement M3’s exact Todo/experiment lineage and write-time gate as a separately reviewable behavior cha
Outcome / 目标 验收先观测后治理的长程可靠性诊断。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree. Canonical design: RFC. Roadmap: S10/S11/S13, under #4574. Design acceptance is distinct from implementation, live qualification and promotion. Current boundary Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim. The default-off reliability-diagnostics prototype and dsh-session-events adapter ship. The capability README explicitly withholds P0 exit pending C0/C1 and measured overhead; the RFC also requires retention/deletion policy. Work remaining Close P0’s integrity, non-interference, retention and real-observer evidence, then assess the P1 diagnostic pilot against a declared outcome. Progress to a governed seam or repeatable deployment only through the RFC’s own evidence and authority gates; retain an explicit stop/n
Outcome / 目标 完成外部证据研究的真实 provider 与用户回读。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree. Canonical design: RFC. Roadmap: S6/S8, under #4574. Design acceptance is distinct from implementation, live qualification and promotion. Current boundary Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim. #4813 shipped discover/plan/receipt/admit/retire through a typed TS owner and CLI. The RFC explicitly distinguishes observing a caller-presented receipt from proving provider execution, and names frontend/Lark as companion work. Work remaining Reuse the exact-plan lifecycle with one existing research method and one supported connector where needed; retain their own execution/permission owners. Expose the same plan, source provenance, parent admission, downstream use and retirement facts in the affected product
Outcome / 目标 验收 benchmark study 上传、回读与看板完整链路。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree. Canonical design: RFC. Roadmap: S11/S12, under #4574. Design acceptance is distinct from implementation, live qualification and promotion. Current boundary Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim. The contract/reducers, local upload CLI and read-only dashboard already exist; #3878 binds case insights to terminal runs. Treat this as integrated acceptance and current-checkpoint reconciliation, not a new dashboard or uploader. Work remaining Map RFC acceptance to the shipped CLI → local upload/readback → derived campaign/arm/case/run views and close any evidenced integration gaps. Reconcile the RFC delivery checkpoint with that evidence. If every v0 criterion is already satisfied, close with evidence
Outcome / 目标 交付 IM、LoopX 与 OpenViking 三方协作契约。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree. Canonical design: RFC. Roadmap: S3/S6/S9, under #4574. Design acceptance is distinct from implementation, live qualification and promotion. Current boundary Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim. IM delivery, canonical work/claim authority and memory providers already exist separately. The RFC index does not claim the integrated three-owner journey. Memory retrieval must not become claim or execution authority. Work remaining Compose the RFC’s first real room projection and revision-guarded claim interaction through existing Goal Channel and Todo owners; return the canonical receipt beside the interaction. Keep scoped OpenViking retrieval read-only; carry authorized artifact references and recheck authori
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 loopx-project/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 loopx-project/loopx acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 14.3% were successfully merged into the primary branch.
loopx-project/loopx has a recorded first-timer success rate of 20.0%. 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 68.0 places loopx-project/loopx in the Welcoming tier.
The external pull request merge rate is 14.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, loopx-project/loopx currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for loopx-project/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.