CUDA on non-NVIDIA GPUs
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 76%
Response Time: 7d
First Timer Success: 67%
vosen/ZLUDA has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vosen/ZLUDA respond to incoming external pull requests in approximately 175.3 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 62.7 places vosen/ZLUDA in the A tier.
The external contributor pull request merge rate for vosen/ZLUDA is 75.9%, based on public PR activity from non-core contributors.
vosen/ZLUDA currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in vosen/ZLUDA. 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/vosen/ZLUDA?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~114 hours (95% approval). Large PRs (>500 lines) take ~841 hours (34% approval). Keep your diff compact for rapid review.
Expected outcome: There's one zluda.exe that works for both 32-bit and 64-bit executables
Expected outcome: All fp64 operations are bit-accurate as defined by PTX spec (https://docs.nvidia.com/cuda/parallel-thread-execution/index.html) Comments: fp32 and lower is already accurate fp64 is pretty much only used in HPC, so there's been no pressing need to improve it. With ZLUDA not supporting sever gpus this has been somewhat low priority, but since mi450x is shaping up to be supported by ZLUDA, it's getting more relevant We have a test suite here to test it: https://github.com/vosen/ptx_tests
Expected outcome: You can launch an application with ZLUDA on Windows without opening a command line Comments: I think a good mode of operation would be to, after double clicking zluda.exe to show an "open file" dialog and then run the selected executable Also allow drag&drop? Consider adding a "link-maker" .exe: drop your exe on it and get a link Pop up an error/warning when a user tries to launch a non-ptx kernel
Expected outcome: Compiling large PTX module uses multiple threads Comments: ZLUDA passes are all relatively fast, so there's little reason to divide it between threads, all the time is spent in LLVM Blender is a good target for experiments. They ship single PTX module, it's 12MB of pure text and contains 75 kernels The strategy would be to write a transformation that splits PTX module into separate compilation units, one for each kernel and than compiling them in parallel and linking into a single ELF Extra care has to be applied to non-kernel top-level items: shared memory globals, global memory globals, functions. AMDGPU target and lld have full support for linking, but it will require some care to make sure that linking/visibility attributes are emitted correctly and things link properly
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 vosen/ZLUDA, 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 vosen/ZLUDA acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.9% were successfully merged into the primary branch.
vosen/ZLUDA has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 62.7 places vosen/ZLUDA in the Welcoming tier.
The external pull request merge rate is 75.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vosen/ZLUDA currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for vosen/ZLUDA 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.