The open-source Agent Gallery and Gateway for Codex, Claude Agent SDK, and OpenCode. Developers publish an Agent once behind one HTTP API; users run it in an isolated cloud sandbox—no local harness setup, compute, or runtime infrastructure.
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 71%
Response Time: 3h
First Timer Success: 75%
langgenius/mosoo has a recorded first-timer success rate of 75.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in langgenius/mosoo respond to incoming external pull requests in approximately 2.8 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 70.2 places langgenius/mosoo in the S tier.
The external contributor pull request merge rate for langgenius/mosoo is 71.1%, based on public PR activity from non-core contributors.
langgenius/mosoo does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
The open-source Agent Gallery and Gateway for Codex, Claude Agent SDK, and OpenCode. Developers publish an Agent once behind one HTTP API; users run it in an isolated cloud sandbox—no local harness setup, compute, or runtime infrastructure.
Strict review standards in langgenius/mosoo. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in langgenius/mosoo 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/langgenius/mosoo?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 Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (89% approval). Large PRs (>500 lines) take ~13 hours (32% approval). Keep your diff compact for rapid review.
Area API Summary Mosoo can revoke a bound Agent capability when its Deployment is deleted through Mosoo, but it cannot currently detect a Cloudflare Pages/Worker resource deleted directly through the Cloudflare dashboard or API. D1 can therefore still describe the Deployment and its public binding as live, and the previously issued capability URL can continue to start bound Sessions/Runs. This is control-plane drift. It is intentionally separate from #287 / #317, which close the Mosoo-managed deletion, unbind, and successful-version-rollover paths. Steps to reproduce Deploy an App with a public bound Agent and retain its generated capability URL. Delete the corresponding Pages/Worker resource directly through Cloudflare, without calling the Mosoo deployment deletion flow. Do not alter Mosoo D1 deployment state. Submit a request to the retained capability URL. The exact Cloudflare-console action cannot be reproduced in this local environment because it requires a real remote CF accoun
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 langgenius/mosoo, 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 langgenius/mosoo acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.1% were successfully merged into the primary branch.
langgenius/mosoo has a recorded first-timer success rate of 75.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 70.2 places langgenius/mosoo in the Elite tier.
The external pull request merge rate is 71.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
langgenius/mosoo 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 langgenius/mosoo 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.