Crash-test insurance claim AI agents before production.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
samarailly51-pixel/claimpilot-harness 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 samarailly51-pixel/claimpilot-harness 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 8.0 places samarailly51-pixel/claimpilot-harness in the D tier.
The external contributor pull request merge rate for samarailly51-pixel/claimpilot-harness is 0.0%, based on public PR activity from non-core contributors.
samarailly51-pixel/claimpilot-harness currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in samarailly51-pixel/claimpilot-harness. Reviews community pull requests with focus on project quality.
Discussions in samarailly51-pixel/claimpilot-harness 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/samarailly51-pixel/claimpilot-harness?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Add one fictional claim case demonstrating how a contributor can preserve stable machine-readable fields while providing clear bilingual evidence summaries or companion documentation. Acceptance criteria: Keep case IDs, evidence IDs, tags, and verdicts schema-compatible Do not include real claimant information Document the localization choice in the pull request Pass validation and unit tests
Create a fictional property or auto claim where invoice identifiers, dates, or line items overlap across submissions and require human investigation. Acceptance criteria: Keep fraud as a review signal, not a proven accusation Include at least three evidence items with one meaningful conflict Add or reuse clear taxonomy tags Pass validation and the regression suite
Add one fictional disability claim scenario that tests inconsistent return-to-work dates, missing employer confirmation, and an unsafe automatic approval shortcut. Acceptance criteria: Start from cases/template-case.json Use stable evidence IDs and reusable risk tags Include expected verdict, findings, document requests, citations, and prohibited behavior Pass claimpilot validate, claimpilot suite, and unit tests Include no real personal or medical data
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 samarailly51-pixel/claimpilot-harness, 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 samarailly51-pixel/claimpilot-harness acknowledge new external contributions in approximately -. 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.
samarailly51-pixel/claimpilot-harness 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 ~-. 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 8.0 places samarailly51-pixel/claimpilot-harness 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, samarailly51-pixel/claimpilot-harness currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for samarailly51-pixel/claimpilot-harness 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.