Hyperlight is a lightweight Virtual Machine Manager (VMM) designed to be embedded within applications. It enables safe execution of untrusted code within micro virtual machines with very low latency and minimal overhead.
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 38%
hyperlight-dev/hyperlight has a recorded first-timer success rate of 37.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in hyperlight-dev/hyperlight 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 69.6 places hyperlight-dev/hyperlight in the S tier.
The external contributor pull request merge rate for hyperlight-dev/hyperlight is 72.5%, based on public PR activity from non-core contributors.
hyperlight-dev/hyperlight currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in hyperlight-dev/hyperlight. Prompt code reviews with positive guidance for new 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/hyperlight-dev/hyperlight?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (91% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
Linux+window guard pages tests were added in #1498, however it didn't update the existing linux-only guard page tests to also run on windows. We should update the linux-only guard_page_crash_test to also run on windows using the same pattern added 1498
Currently we don't share any deps in workspace cargo.toml, which we should. We are even using different versions of the same crate in some instances
more of a meta comment, but I've always felt this was fragile. Is there any reason we don't just replace all the steps in ci with the just commands? that way they stay in sync automatically. Originally posted by @jsturtevant in #1198 (comment)
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 hyperlight-dev/hyperlight, 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 hyperlight-dev/hyperlight acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.5% were successfully merged into the primary branch.
hyperlight-dev/hyperlight has a recorded first-timer success rate of 37.5%. Repositories ranked Elite 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 69.6 places hyperlight-dev/hyperlight in the Elite tier.
The external pull request merge rate is 72.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, hyperlight-dev/hyperlight 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 hyperlight-dev/hyperlight 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.