Run your real agent with and without your skills, MCPs, and rules. See which ones actually help, and what they cost in tokens. Supports Claude Code, Codex, Pi, and Hermes.
C-Rank Grade: D (Risky) - 27/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
edonadei/caliper has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in edonadei/caliper respond to incoming external pull requests in approximately 0.4 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 26.7 places edonadei/caliper in the D tier.
The external contributor pull request merge rate for edonadei/caliper is 0.0%, based on public PR activity from non-core contributors.
edonadei/caliper currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in edonadei/caliper welcoming community pull requests and bug fixes.
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/edonadei/caliper?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~2 hours (29% approval). Keep your diff compact for rapid review.
Remaining problem Claude Code maps recorded provider status codes to MODEL_UNAVAILABLE, AUTH and RATE_LIMITED. Codex, Pi and Hermes still return generic OTHER failures for nonzero judge CLI exits. That preserves the failure, but cannot offer the same precise diagnosis. Reviewed 2026-10-03 against main at 0f94c3f. Already delivered #111 / PR #119 added PromptResult.unclassified_failure; Codex now reaches OTHER consistently with the shared CLI harness. The former first acceptance item is complete. #139 makes a classified MODEL_UNAVAILABLE judge failure stop the run with HarnessConfigurationError and the --judge-model hint. New tests must cover that stop, rather than expecting a per-attempt judge_error. PR #237 introduced AgentReport for attempt-output reading. This issue is about the separate bare-prompt judge path: do not conflate attempt refusal handling with judge failure classification. Current implementation pointers Claude Code: _classify_claude_prompt_failure / _envelope_failur
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 edonadei/caliper, 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 edonadei/caliper acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
edonadei/caliper has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 26.7 places edonadei/caliper in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, edonadei/caliper 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 edonadei/caliper 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.