Thin, unified, C++-flavored wrappers for the CUDA APIs
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
eyalroz/cuda-api-wrappers has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eyalroz/cuda-api-wrappers 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 7.5 places eyalroz/cuda-api-wrappers in the D tier.
The external contributor pull request merge rate for eyalroz/cuda-api-wrappers is 0.0%, based on public PR activity from non-core contributors.
eyalroz/cuda-api-wrappers currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in eyalroz/cuda-api-wrappers. Reviews community pull requests with focus on project quality.
Discussions in eyalroz/cuda-api-wrappers focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/eyalroz/cuda-api-wrappers?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Description When compiling a .cu file with CUDA 12, using cuda-api-wrappers together with Thrust leads to cuda::span redefinition and ambiguous constructor errors. The same code compiles fine under CUDA 11. Minimal Reproducer #include <cuda/api.hpp> // Must come first to trigger the error #include <thrust/device_vector.h> #include <thrust/execution_policy.h> void trigger() { cuda::span<float> s{nullptr, 0}; } int main() { trigger(); return 0; } Compile with: nvcc -x cu -std=c++20 -arch=sm_75 -cudart shared \ -I <path-to-cuda-api-wrappers> \ -I <CUDA-include-path> \ -c main.cpp -o main.obj Observed Behavior Errors like: error C2977: 'cuda::span': too many template arguments error C2641: cannot deduce template arguments for 'cuda::span' error C2780: expects 0 arguments - 2 provided Notes The issue only appears when compiling the file as a CUDA source (-x cu) in CUDA 12. Treated as a normal C++ file, the code compiles fine. Likely related to changes in CUDA 1
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 eyalroz/cuda-api-wrappers, 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 eyalroz/cuda-api-wrappers acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
eyalroz/cuda-api-wrappers has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places eyalroz/cuda-api-wrappers in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eyalroz/cuda-api-wrappers 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 eyalroz/cuda-api-wrappers 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.