Vector search engine inside Milvus, integrating FAISS, HNSW, DiskANN.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 73%
Response Time: 4d
First Timer Success: 87%
zilliztech/knowhere has a recorded first-timer success rate of 86.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zilliztech/knowhere respond to incoming external pull requests in approximately 87.9 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 65.1 places zilliztech/knowhere in the A tier.
The external contributor pull request merge rate for zilliztech/knowhere is 73.2%, based on public PR activity from non-core contributors.
zilliztech/knowhere currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in zilliztech/knowhere.
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/zilliztech/knowhere?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~57 hours (92% approval). Large PRs (>500 lines) take ~422 hours (33% approval). Keep your diff compact for rapid review.
Is there an existing issue for this? I have searched the existing issues. No directly matching open issue was identified in the catalog duplicate check. Recheck the target branch and in-flight PRs with a maintainer before claiming this task. Project Catalog ID: K02 Difficulty: easy Estimated incremental effort: 3–5 hours Reduce one measured max/min reduction cost over an existing distance matrix. Implementation scope Use maintainer-provided baseline/dispatch/microbenchmarks; implement one instruction-set path with scalar fallback, tails and unaligned input. Acceptance criteria Preserve existing floating-point/NaN/tie semantics; report kernel and full-rerank impact and avoid submitting an equivalent compiler optimization as new work. Dependencies No numbered project prerequisite. The preparation conditions below still apply. Boundaries and preparation One reduction hotspot and one ISA, not fused distance computation or a new SIMD framework. The estimate assumes familiarity with the
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 zilliztech/knowhere, 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 zilliztech/knowhere acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.2% were successfully merged into the primary branch.
zilliztech/knowhere has a recorded first-timer success rate of 86.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 65.1 places zilliztech/knowhere in the Welcoming tier.
The external pull request merge rate is 73.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zilliztech/knowhere 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 zilliztech/knowhere 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.