Centaur is frontier, agentic infrastructure that you own. Centaur is like Claude Tag, but open source and on steroids.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 61%
Response Time: 13h
First Timer Success: 47%
paradigmxyz/centaur has a recorded first-timer success rate of 47.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in paradigmxyz/centaur respond to incoming external pull requests in approximately 12.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 59.6 places paradigmxyz/centaur in the A tier.
The external contributor pull request merge rate for paradigmxyz/centaur is 61.4%, based on public PR activity from non-core contributors.
paradigmxyz/centaur currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active Python repository in paradigmxyz/centaur with ongoing community development and issue triage.
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/paradigmxyz/centaur?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (77% approval). Large PRs (>500 lines) take ~62 hours (28% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
Docker environment for developing, deploying, and running Frappe applications (ERPNext and custom apps) in production and development
Open-source framework for conversational voice AI agents
异环 后台副本挂机 Automation for Neverness to Everness
Integrate Hermes Agent as another Centaur harness/runtime option. Where it fits: Centaur's current architecture keeps Slackbot and other clients thin: they call spawn -> message -> execute, the API assigns or reuses a sandbox runtime, and the sandbox runs the selected harness command (codex, claude-code, amp, etc.) while normalized events stream back through /agent/threads/{thread}/events. Hermes should fit at that harness layer, not as a separate Slackbot path. Suggested scope: Add a Hermes harness/engine entry alongside the existing sandbox harnesses. Add the sandbox command/config needed to launch Hermes Agent inside the agent image. Normalize Hermes output into Centaur's canonical execution events so Slackbot, API clients, and final delivery keep working through the existing event stream. Document how to select Hermes as a harness. Acceptance criteria: A caller can request Hermes through the existing agent API harness selection flow. Hermes runs inside the existing Kubernetes sa
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 paradigmxyz/centaur, 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 paradigmxyz/centaur acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.4% were successfully merged into the primary branch.
paradigmxyz/centaur has a recorded first-timer success rate of 47.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 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 59.6 places paradigmxyz/centaur in the Welcoming tier.
The external pull request merge rate is 61.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, paradigmxyz/centaur currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for paradigmxyz/centaur 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.