Mooncake is the serving platform for Kimi, a leading LLM service provided by Moonshot AI.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 68%
kvcache-ai/Mooncake has a recorded first-timer success rate of 68.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kvcache-ai/Mooncake 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 66.8 places kvcache-ai/Mooncake in the A tier.
The external contributor pull request merge rate for kvcache-ai/Mooncake is 64.4%, based on public PR activity from non-core contributors.
kvcache-ai/Mooncake currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in kvcache-ai/Mooncake. Maintains strict focus on technical quality and test standards.
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/kvcache-ai/Mooncake?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Bug Report Summary When an HA standby starts from a batch OpLog snapshot, the snapshot state and recovery cursor are restored successfully, but the exported ha_oplog_applied_sequence_id metric remains at its initial value. This makes the metric disagree with the standby's actual recovery position. Reproduction The issue is reproducible with a snapshot whose recovered sequence is 117 and which has no incremental OpLog entries to apply after the snapshot: Create and publish a valid batch OpLog snapshot covering sequence 117. Start an HA standby with snapshot bootstrap enabled. Allow snapshot recovery to complete and the standby to enter WATCHING. Read the standby metrics and synchronization status. Observed result: recovery log: snapshot/applied = 117 OpLogApplier expected: 118 snapshot applied batch: 51 standby state: WATCHING sync status applied: 117 ha_oplog_applied_sequence_id: 0 The standby's internal cursor and synchronization status show that sequence 117
How this list was produced Started as a static pass over: the C++ shim (mooncake-transfer-engine/src/transfer_engine.cpp, use_tent_ branches) the Python wrapper (mooncake-integration/transfer_engine/transfer_engine_py.cpp) inference-engine call sites that use mooncake.engine.TransferEngine Local runtime (2026-09-10, installed TENT wheel, 1P1D PD) then confirmed some items and left others unverified. Status below is as of 2026-09-17 (origin/main c4d632888b). Please still reproduce on your tree before treating a remaining item as confirmed. Why the compatibility layer We are wiring inference engines to TENT's native APIs, but that work is not finished. Until it is, we use the classic TE compatibility layer (MC_USE_TENT=1) to validate TENT runtime stability against existing callers (PD disaggregation and others). This RFC tracks gaps in that layer. It is not the native-API migration itself. Summary MC_USE_TENT=1 (and MC_USE_TEV1=1) is meant to run existing mooncake::TransferEngine / moo
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 kvcache-ai/Mooncake, 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 kvcache-ai/Mooncake acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.4% were successfully merged into the primary branch.
kvcache-ai/Mooncake has a recorded first-timer success rate of 68.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 66.8 places kvcache-ai/Mooncake in the Welcoming tier.
The external pull request merge rate is 64.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kvcache-ai/Mooncake 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 kvcache-ai/Mooncake 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.