Fast search engine on object storage, with full text search, vectors, and SQL, natively on Parquet.
C-Rank Grade: S (Elite) - 76/100
External PR Merge Rate: 88%
Response Time: 1d
First Timer Success: 85%
infino-ai/infino has a recorded first-timer success rate of 84.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in infino-ai/infino respond to incoming external pull requests in approximately 24.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 75.5 places infino-ai/infino in the S tier.
The external contributor pull request merge rate for infino-ai/infino is 88.2%, based on public PR activity from non-core contributors.
infino-ai/infino currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in infino-ai/infino. Reviews community pull requests with focus on project quality.
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/infino-ai/infino?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (40% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Rust.
Open-source developer platform to power your entire infra and turn scripts into webhooks, workflows and UIs. Fastest workflow engine (13x vs Airflow). Open-source alternative to Retool and Temporal.
A smart USB drive for Tesla Dashcam - extended storage, auto archive, web viewer
Native TypeScript game engine — compiles to Metal, DirectX 12, Vulkan, and OpenGL
Follow-up to #466 (which adds recall_while_ingest). While investigating recall-at-scale (#436) and the in-place cell split (#450), we ended up with two ground-truth mechanisms in the vector benches, plus some avoidable cost. This tracks the cleanup. Background The vector bench grades against a full-corpus exact oracle: it prepares the entire corpus to disk (mmap — ~400 GB at 100M×1024) and brute-forces top-k, caching the oracle in a bin (corpus/grading.rs). The bin already persists the query vectors and the labels. recall_while_ingest (#466) grades against an inline running ground truth — per-query top-k min-heaps updated as each batch streams by — so the corpus is never materialized. But it doesn't persist that GT. Follow-ups Load queries + GT from the oracle bin; don't regenerate the corpus. On a reopen / read-sweep the read path has a valid cached oracle but still regenerates the ~400 GB corpus solely to rebuild the query vectors for validation (generate_realistic_queries
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 infino-ai/infino, 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 infino-ai/infino acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.2% were successfully merged into the primary branch.
infino-ai/infino has a recorded first-timer success rate of 84.6%. Repositories ranked Elite 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 75.5 places infino-ai/infino in the Elite tier.
The external pull request merge rate is 88.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, infino-ai/infino 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 infino-ai/infino 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.