Lightweight type-1 Rust Hypervisor for edge devices
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 55%
Response Time: 8d
First Timer Success: 33%
syswonder/hvisor has a recorded first-timer success rate of 33.3%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in syswonder/hvisor respond to incoming external pull requests in approximately 201.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 53.0 places syswonder/hvisor in the B tier.
The external contributor pull request merge rate for syswonder/hvisor is 54.9%, based on public PR activity from non-core contributors.
syswonder/hvisor currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in syswonder/hvisor. 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/syswonder/hvisor?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 Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~131 hours (69% approval). Large PRs (>500 lines) take ~965 hours (25% approval). Keep your diff compact for rapid review.
Affected upstream snapshots hvisor: syswonder/hvisor, branch dev, commit 9dbacc423100c1deb2e7d3be6d1bd6bef06e520c hvisor-tool: syswonder/hvisor-tool, branch main, commit e4f6931dc9d26e9f748eacd37f3b982fd66778b0 Architecture/platform: LoongArch64, Loongson 3A6000 public board with 7A2000 Related hvisor-tool issue: syswonder/hvisor-tool#109 cc @li041 Summary The current LoongArch path has several coupled interrupt-state problems. The common issue is that software events, guest IPI actions, guest GINTC HWI bits, Virtio device status, and the backend clear request are not represented as one-to-one state transitions. The result can be lost hvisor events, imprecise guest IPI delivery, global clearing of unrelated guest HWIs, random Virtio console stalls, and a root serial console that appears to work through early polling while its real UART interrupt is not connected. This issue describes the complete chain because fixing only one layer can hide the failure without making the protocol cor
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 syswonder/hvisor, 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 syswonder/hvisor acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.9% were successfully merged into the primary branch.
syswonder/hvisor has a recorded first-timer success rate of 33.3%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 53.0 places syswonder/hvisor in the Solid tier.
The external pull request merge rate is 54.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, syswonder/hvisor 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 syswonder/hvisor 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.