DRAKVUF Black-box Binary Analysis
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 60%
Response Time: 2d
First Timer Success: 50%
tklengyel/drakvuf has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tklengyel/drakvuf respond to incoming external pull requests in approximately 54.9 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 48.0 places tklengyel/drakvuf in the B tier.
The external contributor pull request merge rate for tklengyel/drakvuf is 60.0%, based on public PR activity from non-core contributors.
tklengyel/drakvuf currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in tklengyel/drakvuf. 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/tklengyel/drakvuf?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~36 hours (75% approval). Large PRs (>500 lines) take ~263 hours (27% approval). Keep your diff compact for rapid review.
The following regression is observed with Xen 4.21 running Windows 10 guests with the viridian=1 flag set in the domain config: (XEN) d1v1 Unexpected vmexit: reason 49 (XEN) domain_crash called from arch/x86/hvm/vmx/vmx.c:4849 (XEN) Domain 1 (vcpu#1) crashed on cpu#2: (XEN) ----[ Xen-4.21.0 x86_64 debug=y Not tainted ]---- (XEN) CPU: 2 (XEN) RIP: 0010:[<fffff806622b1967>] (XEN) RFLAGS: 0000000000050282 CONTEXT: hvm guest (d1v1) (XEN) rax: fffff67e27a809cc rbx: 0000000000000000 rcx: fffff67e27a809d0 (XEN) rdx: 00000b1985be6000 rsi: 00000197ad6669cc rdi: fffff67e27a809cc (XEN) rbp: ffff87829aad8519 rsp: ffff87829aad83c8 r8: 0000000000000358 (XEN) r9: 0000000000000000 r10: ffff9183464a4910 r11: 00000197ad666d24 (XEN) r12: 0000000000000358 r13: ffff87829aad84c0 r14: 000000000000006e (XEN) r15: ffff87829aad8498 cr0: 0000000080050031 cr4: 0000000000370678 (XEN) cr3: 000000003e6a7002 cr2: 00007ffaa8d3e510 (XEN) fsb: 0000000000000000 gsb: ffffe6810ffa80
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 tklengyel/drakvuf, 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 tklengyel/drakvuf acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.0% were successfully merged into the primary branch.
tklengyel/drakvuf has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 48.0 places tklengyel/drakvuf in the Solid tier.
The external pull request merge rate is 60.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tklengyel/drakvuf 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 tklengyel/drakvuf 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.