Use Cursor Pro models in OpenCode via HTTP proxy with OAuth
C-Rank Grade: D (Risky) - 17/100
External PR Merge Rate: -
Response Time: 2d
First Timer Success: -
Nomadcxx/opencode-cursor 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 Nomadcxx/opencode-cursor respond to incoming external pull requests in approximately 49.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 16.5 places Nomadcxx/opencode-cursor in the D tier.
The external contributor pull request merge rate for Nomadcxx/opencode-cursor is 0.0%, based on public PR activity from non-core contributors.
Nomadcxx/opencode-cursor currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Use Cursor Pro models in OpenCode via HTTP proxy with OAuth
Active maintainer team in Nomadcxx/opencode-cursor 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/Nomadcxx/opencode-cursor?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~32 hours (81% approval). Large PRs (>500 lines) take ~237 hours (29% approval). Keep your diff compact for rapid review.
Description after installing opencode-cursor, on the desktop app, when opencode start to edit files, instead of showing editing preview and what changed, it only shows oc_edit tool execution. reproduced on both my remote vps and my local macos after removing the plugin, Patch start to show up again Expected behavior the conversations on older version shows correct patch preview OpenCode version v1.17.9 Steps to reproduce install opencode-cursor plugin open opencode desktop ask opencode to edit a file see oc_edit instead of just Patch with edit preview Screenshot and/or share link https://opncd.ai/share/P0zpbT5F Operating System macOS 15.5 (24F74)
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 Nomadcxx/opencode-cursor, 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 Nomadcxx/opencode-cursor acknowledge new external contributions in approximately 2 days+. 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.
Nomadcxx/opencode-cursor 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 ~2 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 16.5 places Nomadcxx/opencode-cursor 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, Nomadcxx/opencode-cursor 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 Nomadcxx/opencode-cursor 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.