wesl-rs: a compiler for WESL (WGSL Extended) shaders.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 80%
Response Time: 2h
First Timer Success: 100%
webgpu-tools/wesl-rs has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in webgpu-tools/wesl-rs respond to incoming external pull requests in approximately 1.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 73.6 places webgpu-tools/wesl-rs in the S tier.
The external contributor pull request merge rate for webgpu-tools/wesl-rs is 80.0%, based on public PR activity from non-core contributors.
webgpu-tools/wesl-rs currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in webgpu-tools/wesl-rs. Reviews community pull requests with focus on project quality.
Discussions in webgpu-tools/wesl-rs 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/webgpu-tools/wesl-rs?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~8 hours (36% approval). Keep your diff compact for rapid review.
in #229 the CI failed because wesl-test depends on bevy-wgsl, which depended on wesl version 4.4.0. I forgot to bump the version. In the lockfile, there were two entries for wesl. This could have been caught.
wesl-rs uses a HashMap for a lot of things. Rust's HashMaps are resistant to HashDoS attacks and use a bit of randomness to do so. One consequence is that the order of .iter() will change across runs. However, a compiler should be as deterministic as possible. So we should prevent using the .iter functions and sometimes use https://docs.rs/indexmap/latest/indexmap/ instead of a hash map. This is also what naga does https://wgpu.rs/doc/naga/type.FastIndexSet.html . Bonus points for switching to a faster hasher.
Currently stripping is controlled by 3 unrelated booleans. It'd be nice if an enum were used to encode the valid states. I propose something like this pub struct CompileOptions { ... pub strip: Option<StripOptions>, } pub enum StripOptions { /// Strip everything that is not reachable from the main module entrypoints, const_asserts and pipeline-overridable constants. Unreachable, /// Keep everything in the main module, regardless of reachability. MainModule, /// Keep only the specified list of declarations in the main module. Keep(Vec<String>), }
mat2x2() -> "matrix components are incompatible" should say something more useful
proc-macro-error2 has an unmaintained advisory. They recommend manyhow and proc-macro2-diagnostics as alternatives.
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 webgpu-tools/wesl-rs, 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 webgpu-tools/wesl-rs acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.0% were successfully merged into the primary branch.
webgpu-tools/wesl-rs has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 73.6 places webgpu-tools/wesl-rs in the Elite tier.
The external pull request merge rate is 80.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, webgpu-tools/wesl-rs currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for webgpu-tools/wesl-rs 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.