Exo is an agent + harness architecture that is fully recursive, able to safely edit all aspects of itself at runtime to get better at your tasks.
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 55%
Response Time: -
First Timer Success: 27%
exoharness/exo has a recorded first-timer success rate of 26.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in exoharness/exo 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 63.9 places exoharness/exo in the A tier.
The external contributor pull request merge rate for exoharness/exo is 55.5%, based on public PR activity from non-core contributors.
exoharness/exo currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (62% critical review signals). Ensure PRs strictly follow guidelines before requesting review in exoharness/exo.
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/exoharness/exo?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (69% approval). Large PRs (>500 lines) take ~115 hours (25% approval). Keep your diff compact for rapid review.
The chat REPL in `crates/cli/src/tui.rs` handles slash commands (`/snapshot`, `/snapshots`, `/rewind `, `/help`, `/history`, `/quit`) with ad-hoc match-on-string logic, plus a hand-rolled `print_help` whose contents have to be kept in sync with the match arms manually. Switch to a real CLI library (clap-derive seems natural since the rest of the binary already uses it) so commands are declared once with their args + help text and the parser/router/help-printer fall out automatically. Cuts the drift risk and makes adding new slash commands a one-line change. Surfaced in review of #20: #20 (comment)
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 exoharness/exo, 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 exoharness/exo acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.5% were successfully merged into the primary branch.
exoharness/exo has a recorded first-timer success rate of 26.7%. 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 63.9 places exoharness/exo in the Welcoming tier.
The external pull request merge rate is 55.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, exoharness/exo 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 exoharness/exo 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.