cuda-oxide is a Rust-to-CUDA compiler that lets you write (SIMT) GPU kernels in safe(ish), idiomatic Rust. It compiles standard Rust code directly to PTX — no DSLs, no foreign language bindings, just Rust.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 75%
Response Time: 1d
First Timer Success: 72%
NVlabs/cuda-oxide has a recorded first-timer success rate of 72.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in NVlabs/cuda-oxide respond to incoming external pull requests in approximately 25.7 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 65.4 places NVlabs/cuda-oxide in the A tier.
The external contributor pull request merge rate for NVlabs/cuda-oxide is 74.6%, based on public PR activity from non-core contributors.
NVlabs/cuda-oxide does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in NVlabs/cuda-oxide. 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/NVlabs/cuda-oxide?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 Monday - Wednesday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (93% approval). Large PRs (>500 lines) take ~123 hours (34% approval). Keep your diff compact for rapid review.
Summary #668 ("docs(examples): tma_multicast does run on consumer Blackwell", merged 2026-08-06) corrected the tma_multicast example on the strength of your RTX 5090 measurement: the sm_100a tma_multicast PTX JIT-loads and passes on an RTX 5090, so the "consumer Blackwell does not support TMA multicast" fallback text is outdated It fixed the two places it found — the module header and the runtime println! — and missed README.md entirely. That file still carries four separate assertions of the claim #668 removed, so the example's own directory now contradicts itself. My PR, my miss; filing rather than fixing blind because the second half below needs a call I cannot make. The four stale passages All in crates/rustc-codegen-cuda/examples/tma_multicast/README.md: 1. L116 — heading groups sm_120 with the failing case ### On Consumer Blackwell (sm_120) or Hopper (sm_90): 2. L119-124 — a sample transcript showing a failure you measured as a success GPU Compute Capability: sm_120
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 NVlabs/cuda-oxide, 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 NVlabs/cuda-oxide acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.6% were successfully merged into the primary branch.
NVlabs/cuda-oxide has a recorded first-timer success rate of 72.2%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 65.4 places NVlabs/cuda-oxide in the Welcoming tier.
The external pull request merge rate is 74.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
NVlabs/cuda-oxide does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for NVlabs/cuda-oxide 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.