A super light-weight embedded code search engine CLI (AST based) that just works - improves speed and efficiency for coding agent 🌟 Star if you like it!
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 70%
Response Time: 1d
First Timer Success: 60%
cocoindex-io/cocoindex-code has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cocoindex-io/cocoindex-code respond to incoming external pull requests in approximately 35.2 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 62.3 places cocoindex-io/cocoindex-code in the A tier.
The external contributor pull request merge rate for cocoindex-io/cocoindex-code is 70.0%, based on public PR activity from non-core contributors.
cocoindex-io/cocoindex-code currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in cocoindex-io/cocoindex-code. Prompt code reviews with positive guidance for new contributors.
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/cocoindex-io/cocoindex-code?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~23 hours (88% approval). Large PRs (>500 lines) take ~169 hours (32% approval). Keep your diff compact for rapid review.
Hey there, I followed the installation steps but I got stuck at an issue. The issue is that Cline fails to connect to the MCP server. My environment OS: Windows 11 IDE: VSCode Coding agent: Cline (VSCode extension) Issue What gets written in Cline's MCP Servers window: Error: Not in an initialized project directory. Run `ccc init` in your project root to get started. MCP error -32000: Connection closed note that this gets shown even after it got initialized using the init command. Steps I took pipx install 'cocoindex-code[full]' (with sentence-transformers) Added this to my cline_mcp_settings.json: { "github.com/cocoindex-io/cocoindex-code": { "command": "C:\\Users\\user\\.local\\bin\\ccc.exe", // I use windows and didnt setup PATH for it hence the full path here "args": [ "mcp" ], "disabled": false, "autoApprove": [] } } After this point, it gets registered in Cline's MCP Servers window, but it show
Hello! Is there any chance Salesforce Apex language could be supported? It's akin to the Java language. Thanks for your consideration.
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 cocoindex-io/cocoindex-code, 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 cocoindex-io/cocoindex-code acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
cocoindex-io/cocoindex-code has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 62.3 places cocoindex-io/cocoindex-code in the Welcoming tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cocoindex-io/cocoindex-code currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for cocoindex-io/cocoindex-code 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.