🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 82%
Response Time: -
First Timer Success: 100%
valeriansaliou/sonic has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in valeriansaliou/sonic respond to incoming external pull requests in approximately 0.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 65.0 places valeriansaliou/sonic in the A tier.
The external contributor pull request merge rate for valeriansaliou/sonic is 82.4%, based on public PR activity from non-core contributors.
valeriansaliou/sonic currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Established Rust ecosystem in valeriansaliou/sonic. Maintains structured code review standards for external 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/valeriansaliou/sonic?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Typo correction can have a big impact on QUERY performance (> ×5 response time in some tests) and results (correcting too many typos can yield weird results). We should add a configuration key to customize the word length → typo factor mapping, so users can tweak or disable it as desired.
I might be wrong and it might just be about countb (which behaves surprinsingly), but flusho seems to not remove orphan terms from the index. Maybe it was just not designed for it, but I don’t remember reading about this. #[test] fn flusho() { let ctx = start_empty(|command| command); let multiplexer = SonicMultiplexer::new().unwrap(); let ingest = SonicChannelIngestBlocking::connect(ctx.addr, "SecretPassword", &multiplexer).unwrap(); let control = SonicChannelControlBlocking::connect(ctx.addr, "SecretPassword", &multiplexer).unwrap(); ingest .push("collection", "bucket", "object:1", "foo bar baz") .unwrap(); ingest .push("collection", "bucket", "object:2", "foo aaa") .unwrap(); control.trigger_consolidate().unwrap(); let res = ingest.countb("collection", "bucket").unwrap(); assert_eq!(res, 4); let res = ingest.flusho("collection", "bucket", "object:1").unwrap(); assert_eq!(res, 3);
The tokenizer-chinese feature uses jieba-rs, which only supports Mandarin Chinese word segmentation. Chinese regional dialects (Cantonese, Hokkien, Hakka) fail to segment correctly. Test Results Same sentence ("we are going shopping today") in four dialects, using jieba-rs 0.7.4: Mandarin (correct — 5 tokens): ["我们", "今天", "去", "买", "东西"] Cantonese (broken — 6 tokens, compound words split): ["我", "哋", "今日", "去", "買", "嘢"] Hokkien (badly broken — 7 tokens): ["阮", "今", "仔", "日", "去", "買", "物件"] Hakka (nearly character-by-character — 9 tokens): ["我", "等", "今", "晡", "日", "去", "買", "東", "西"] Impact Cantonese alone has 85+ million speakers. Hokkien has 50+ million. Hakka has 45+ million. These populations are underserved by any search tool that relies solely on jieba-rs for Chinese tokenization. Suggestion Consider supporting additional tokenizer features for regional Chinese dialects, following the same pattern as token
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 valeriansaliou/sonic, 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 valeriansaliou/sonic acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.4% were successfully merged into the primary branch.
valeriansaliou/sonic has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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.0 places valeriansaliou/sonic in the Welcoming tier.
The external pull request merge rate is 82.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, valeriansaliou/sonic currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for valeriansaliou/sonic 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.