DIY your own agent team harness for long-horizon agent work
C-Rank Grade: B (Solid) - 44/100
External PR Merge Rate: 13%
Response Time: 18d
First Timer Success: -
yangheng95/opencorvus has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in yangheng95/opencorvus respond to incoming external pull requests in approximately 429.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 43.7 places yangheng95/opencorvus in the B tier.
The external contributor pull request merge rate for yangheng95/opencorvus is 13.0%, based on public PR activity from non-core contributors.
yangheng95/opencorvus currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
DIY your own agent team harness for long-horizon agent work
Active maintainer team in yangheng95/opencorvus welcoming community pull requests and bug fixes.
Discussions in yangheng95/opencorvus 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/yangheng95/opencorvus?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~279 hours (16% approval). Large PRs (>500 lines) take ~2061 hours (15% approval). Keep your diff compact for rapid review.
Help validate a published CLI archive We need independent Linux and macOS startup reports for OpenCorvus v0.0.63-beta. You can contribute a report without changing code, configuring a model provider, or buying model credits. Pick one operating system and architecture you already use; one report is useful. Maintainer coverage so far is limited to the published Windows x64 command-line archive: matching release checksum, version/help, doctor module checks, and the initial bundled webpage. That does not establish Linux/macOS startup or successful model work. Bounded task Choose the matching opencorvus-linux-*.tar.gz or opencorvus-darwin-*.tar.gz asset from the linked release. Record the exact asset name and download SHA256SUMS from that same release. Verify the archive's SHA-256 against that file, then extract into a new directory. Report the checksum and whether it matches. Set OPENCORVUS_HOME to a new, empty disposable directory for these commands so this check has its own application
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 yangheng95/opencorvus, 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 yangheng95/opencorvus acknowledge new external contributions in approximately 17 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 13.0% were successfully merged into the primary branch.
yangheng95/opencorvus has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 days+. 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 43.7 places yangheng95/opencorvus in the Solid tier.
The external pull request merge rate is 13.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, yangheng95/opencorvus 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 yangheng95/opencorvus 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.