A cross-platform, safe, pure-Rust graphics API.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 70%
Response Time: -
First Timer Success: 58%
gfx-rs/wgpu has a recorded first-timer success rate of 57.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in gfx-rs/wgpu 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 66.2 places gfx-rs/wgpu in the A tier.
The external contributor pull request merge rate for gfx-rs/wgpu is 70.1%, based on public PR activity from non-core contributors.
gfx-rs/wgpu currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in gfx-rs/wgpu. Ensure PR scope matches issue requirements closely before requesting review.
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/gfx-rs/wgpu?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (88% approval). Large PRs (>500 lines) take ~76 hours (32% approval). Keep your diff compact for rapid review.
Description Vulkan prohibits ImageViews of images that have no sampled/storage usages, but wgpu will happily create a view of a texture with only the COPY_DST usage (or COPY_DST|COPY_SRC) causing a validation error (shown below). Note that, for whatever reason, this does not seem to be happening if the texture only has the COPY_SRC usage - maybe wgpu does some magic to not actually create a texture when it has a meaningless usage like this (it could only be used to copy zero-initialized texels?). Now yes I have no doubt that creating views of textures that have no usages which would allow a texture view to even be used is completely pointless and meaningless, but regardless, I'm pretty sure the whole point of WebGPU is to catch issues like this before they get to the driver level Repro steps use wgpu::*; fn main() { env_logger::builder() .filter_level(log::LevelFilter::Error) .init(); let instance = Instance::default(); let adapter = pollster::block_on(in
Changelog fails because I replaced one non-break space character with a normal whitespace. It likely was a typo originally and my IDE warns about all kinds of invisible or strange characters like that. I can roll it back if you'd really want me to. Originally posted by @nazar-pc in #9953 (comment) My take: We should be checking for characters like this in CI. There's no reason for "odd" whitespace characters in that document.
These lints suggest replacing #[allow] with #[expect] and require a reason to be provided, which improves code quality.
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 gfx-rs/wgpu, 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 gfx-rs/wgpu acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.1% were successfully merged into the primary branch.
gfx-rs/wgpu has a recorded first-timer success rate of 57.6%. Repositories ranked Welcoming 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 66.2 places gfx-rs/wgpu in the Welcoming tier.
The external pull request merge rate is 70.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, gfx-rs/wgpu 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 gfx-rs/wgpu 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.