Local-first search across your workspace, built for humans and AI agents.
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 49%
Response Time: 3h
First Timer Success: 50%
zvec-ai/zvec-grep has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zvec-ai/zvec-grep respond to incoming external pull requests in approximately 3.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 62.3 places zvec-ai/zvec-grep in the A tier.
The external contributor pull request merge rate for zvec-ai/zvec-grep is 48.6%, based on public PR activity from non-core contributors.
zvec-ai/zvec-grep does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in zvec-ai/zvec-grep. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in zvec-ai/zvec-grep 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/zvec-ai/zvec-grep?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (61% approval). Large PRs (>500 lines) take ~14 hours (22% approval). Keep your diff compact for rapid review.
Problem or Motivation Summary zg --install currently supports Codex, Claude Code, Qwen Code, Qoder, OpenCode, Cursor, GitHub Copilot, and VS Code — but not Grok Build (xAI's terminal coding agent, the grok CLI). Grok Build is one of the most widely used terminal coding agents today, in the same category as Claude Code and OpenCode, and first-class support in zg would be very valuable. Why this matters Grok Build is a mainstream terminal AI coding agent that operates directly inside a project workspace. zg's core value — a local-first search layer for humans and agents — applies directly: grok frequently needs to locate code, symbols, and cross-file context by meaning, which is exactly what zvec_grep_search provides. Agent integration is a key differentiator of zg, and missing Grok Build leaves a growing share of agent users without the indexed-search experience. As a user, I use grok-build daily for coding tasks. Without zg integration, I fall back to running zg manually from th
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 zvec-ai/zvec-grep, 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 zvec-ai/zvec-grep acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.6% were successfully merged into the primary branch.
zvec-ai/zvec-grep has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. 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 zvec-ai/zvec-grep in the Welcoming tier.
The external pull request merge rate is 48.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
zvec-ai/zvec-grep does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for zvec-ai/zvec-grep 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.