AI Slop Code RIsk Monitor

gfx-rs/wgpu

A cross-platform, safe, pure-Rust graphics API.

5.4 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for gfx-rs/wgpu, a Rust project with 18,245 GitHub stars. SynthScan examined 405,921 lines of code across 1197 source files, recording 2215 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 5.4 (Moderate pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

5.4
Adjusted Signal
5.4
Raw Pattern Score
100%
Time Factor
2026-10-09
Last Push
18.2K
Stars
Rust
Language
405.9K
Lines of Code
1.2K
Files
2.2K
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 22.9/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 2196 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

Are imports declared and package/API names verified? 4 finding(s).

Agent Over-Engineering Ratio 0.7/100 · LOW

Are wrappers, guards, and repeated structures necessary? 17 finding(s).

PR Review Velocity Impact 24.6/100 · LOW

Which changes need focused human review? 2215 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 4HIGH 0MEDIUM 23LOW 2188

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 2215 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block2153 hits · 2028 pts
SeverityFileLineSnippetContext
LOWwgpu-core-remote/src/hub.rs101/// All the resources tracked by a [`crate::global::Global`].COMMENT
LOWwgpu-core-remote/src/registry.rs1use crate::{COMMENT
LOWwgpu-core-remote/src/global/device.rs81 };COMMENT
LOWwgpu-core-remote/src/global/device.rs101 /// `unsigned long` value, but we can't construct aCOMMENT
LOWwgpu-core-remote/src/global/device.rs701 &self,COMMENT
LOWwgpu-hal/Cargo.toml41] }COMMENT
LOWwgpu-hal/Cargo.toml61# enables the `vulkan` feature in `wgpu-core-deps-linux-android-bsd` which in turn enables theCOMMENT
LOWwgpu-hal/src/lib.rs1//! A cross-platform unsafe graphics abstraction.COMMENT
LOWwgpu-hal/src/lib.rs21//! graphics system. If you need safety, the [`wgpu-core`] crate provides aCOMMENT
LOWwgpu-hal/src/lib.rs41//! unlike `wgpu-core`, which refers to objects by ID.COMMENT
LOWwgpu-hal/src/lib.rs61//! do any mutating work.COMMENT
LOWwgpu-hal/src/lib.rs81//! Vulkan bindings. It's also available on macOS, if you install [MoltenVK].COMMENT
LOWwgpu-hal/src/lib.rs101//!COMMENT
LOWwgpu-hal/src/lib.rs121//! available on the system. For example, [`vulkan::Api::Instance::init`][Ii]COMMENT
LOWwgpu-hal/src/lib.rs141//! - [`Api::Surface`] implements the [`Surface`] trait, which represents aCOMMENT
LOWwgpu-hal/src/lib.rs161//! applications, like web browsers, where the API is available to untrustedCOMMENT
LOWwgpu-hal/src/lib.rs181//! A desire for "defense in depth" may suggest performing additional validationCOMMENT
LOWwgpu-hal/src/lib.rs201//! tracing/replay functionality, which is only available in `wgpu-core`.COMMENT
LOWwgpu-hal/src/lib.rs241extern crate alloc;COMMENT
LOWwgpu-hal/src/lib.rs341#[cfg(all(any(gles, vulkan, metal, dx12), not(webgl)))]COMMENT
LOWwgpu-hal/src/lib.rs581COMMENT
LOWwgpu-hal/src/lib.rs661 ///COMMENT
LOWwgpu-hal/src/lib.rs721 unsafe fn configure(COMMENT
LOWwgpu-hal/src/lib.rs741 /// `self`.COMMENT
LOWwgpu-hal/src/lib.rs761 /// [`SurfaceTexture`] to [`self.discard_texture`], so that it can be reusedCOMMENT
LOWwgpu-hal/src/lib.rs781 ///COMMENT
LOWwgpu-hal/src/lib.rs801 /// After this call, the texture underlying [`SurfaceTexture`] may beCOMMENT
LOWwgpu-hal/src/lib.rs841 /// Returns the HDR / luminance characteristics of the display backingCOMMENT
LOWwgpu-hal/src/lib.rs861 unsafe fn get_presentation_timestamp(&self) -> wgt::PresentationTimestamp;COMMENT
LOWwgpu-hal/src/lib.rs881/// On Vulkan a `Device` corresponds to a logical device ([`VkDevice`]). OtherCOMMENT
LOWwgpu-hal/src/lib.rs901/// which you can use to build [`CommandBuffer`]s holding commands to beCOMMENT
LOWwgpu-hal/src/lib.rs921/// [`CommandBuffer`]: Api::CommandBufferCOMMENT
LOWwgpu-hal/src/lib.rs941 /// Creates a new buffer.COMMENT
LOWwgpu-hal/src/lib.rs961 /// Free `buffer` and any GPU resources it owns.COMMENT
LOWwgpu-hal/src/lib.rs981 ///COMMENT
LOWwgpu-hal/src/lib.rs1001 /// - If this function returns `Ok(mapping)` and `mapping.is_coherent` isCOMMENT
LOWwgpu-hal/src/lib.rs1021 /// [`MAP_READ`]: wgt::BufferUses::MAP_READCOMMENT
LOWwgpu-hal/src/lib.rs1041 ///COMMENT
LOWwgpu-hal/src/lib.rs1201 ///COMMENT
LOWwgpu-hal/src/lib.rs1221 /// [`Fence`]: Api::FenceCOMMENT
LOWwgpu-hal/src/lib.rs1281 }COMMENT
LOWwgpu-hal/src/lib.rs1301 /// submission's commands all complete execution before any of the secondCOMMENT
LOWwgpu-hal/src/lib.rs1321 /// from a [`CommandEncoder`][ce] that was constructed from theCOMMENT
LOWwgpu-hal/src/lib.rs1341 /// typically by calling [`Surface::configure`].COMMENT
LOWwgpu-hal/src/lib.rs1361 signal_fence: (&<Self::A as Api>::Fence, FenceValue),COMMENT
LOWwgpu-hal/src/lib.rs1381 /// ordering between rendering and display.COMMENT
LOWwgpu-hal/src/lib.rs1401 unsafe fn wait_for_idle(&self) -> Result<(), DeviceError>;COMMENT
LOWwgpu-hal/src/lib.rs1421/// - Call methods like `copy_buffer_to_buffer`, `begin_render_pass`,COMMENT
LOWwgpu-hal/src/lib.rs1441/// - The `CommandEncoder` must be in the states described above toCOMMENT
LOWwgpu-hal/src/lib.rs1461 ///COMMENT
LOWwgpu-hal/src/lib.rs1481 /// Return a fresh [`CommandBuffer`] holding the recorded commands.COMMENT
LOWwgpu-hal/src/lib.rs1501COMMENT
LOWwgpu-hal/src/lib.rs1601 /// - If `layout` contains `n` bind group layouts, then any previously setCOMMENT
LOWwgpu-hal/src/lib.rs1621 /// bindings [with dynamic offsets][hdo] in the relevant bind groupCOMMENT
LOWwgpu-hal/src/lib.rs1681 ///COMMENT
LOWwgpu-hal/src/lib.rs1701 ///COMMENT
LOWwgpu-hal/src/lib.rs1721 /// [`end_render_pass`]: CommandEncoder::end_render_passCOMMENT
LOWwgpu-hal/src/lib.rs1741 /// size. On some backends, the binding size is ignored. This means thatCOMMENT
LOWwgpu-hal/src/lib.rs1841 /// - [`begin_query`](CommandEncoder::begin_query)COMMENT
LOWwgpu-hal/src/lib.rs1881 &mut self,COMMENT
2093 more matches not shown…
Decorative Section Separators15 hits · 53 pts
SeverityFileLineSnippetContext
MEDIUMnaga/src/front/wgsl/parse/lexer.rs1267 /// D(𝐡) = ───────────────────────────────────────────────────COMMENT
MEDIUMnaga/src/front/wgsl/parse/lexer.rs1272 Token::DocComment("/// D(𝐡) = ───────────────────────────────────────────────────"),CODE
MEDIUMwgpu/Cargo.toml47# --------------------------------------------------------------------COMMENT
MEDIUMwgpu/Cargo.toml107# --------------------------------------------------------------------COMMENT
MEDIUMwgpu/Cargo.toml124# --------------------------------------------------------------------COMMENT
MEDIUMwgpu/Cargo.toml136# --------------------------------------------------------------------COMMENT
MEDIUMwgpu/Cargo.toml150# --------------------------------------------------------------------COMMENT
MEDIUM⚡wgpu-core/Cargo.toml49# --------------------------------------------------------------------COMMENT
MEDIUM⚡wgpu-core/Cargo.toml59# --------------------------------------------------------------------COMMENT
MEDIUM⚡wgpu-core/Cargo.toml66# --------------------------------------------------------------------COMMENT
MEDIUM⚡wgpu-core/Cargo.toml72# --------------------------------------------------------------------COMMENT
MEDIUMwgpu-core/Cargo.toml91# --------------------------------------------------------------------COMMENT
MEDIUMwgpu-core/Cargo.toml103# --------------------------------------------------------------------COMMENT
MEDIUM⚡wgpu-core/Cargo.toml120# --------------------------------------------------------------------COMMENT
MEDIUM⚡wgpu-core/Cargo.toml130# --------------------------------------------------------------------COMMENT
Structural Annotation Overuse28 hits · 48 pts
SeverityFileLineSnippetContext
LOW⚡wgpu-hal/src/dx12/device_creation.rs72 // Step 1: Get ID3D12SDKConfiguration1 via D3D12GetInterfaceCOMMENT
LOW⚡wgpu-hal/src/dx12/device_creation.rs77 // Step 2: Create device factory with the specified SDK version and pathCOMMENT
LOW.agents/skills/cts-triage/SKILL.md10## Step 0: Divide Into Manageable ChunksCOMMENT
LOW⚡.agents/skills/cts-triage/SKILL.md24## Step 1: Get Overall StatisticsCOMMENT
LOW⚡.agents/skills/cts-triage/SKILL.md34## Step 2: Identify Test SubcategoriesCOMMENT
LOW⚡.agents/skills/cts-triage/SKILL.md42## Step 3: Run Each SubcategoryCOMMENT
LOW.agents/skills/cts-triage/SKILL.md56## Step 4: Analyze Failure PatternsCOMMENT
LOW.agents/skills/cts-triage/SKILL.md69## Step 5: Examine Specific FailuresCOMMENT
LOW.agents/skills/cts-triage/SKILL.md84## Step 6: Check CTS Test SourceCOMMENT
LOW.agents/skills/cts-triage/SKILL.md99## Step 7: Categorize IssuesCOMMENT
LOW.agents/skills/cts-triage/SKILL.md126## Step 8: Identify Root CausesCOMMENT
LOW.agents/skills/cts-triage/SKILL.md152## Step 9: Implement FixesCOMMENT
LOW.agents/skills/cts-triage/SKILL.md163## Step 10: Document FindingsCOMMENT
LOW.agents/skills/cts-triage/SKILL.md217## Step 11: Update CTS Result ListsCOMMENT
LOW.agents/skills/cts-triage/SKILL.md244## Step 12: Verify and BuildCOMMENT
LOW.claude/skills/cts-triage/SKILL.md10## Step 0: Divide Into Manageable ChunksCOMMENT
LOW⚡.claude/skills/cts-triage/SKILL.md24## Step 1: Get Overall StatisticsCOMMENT
LOW⚡.claude/skills/cts-triage/SKILL.md34## Step 2: Identify Test SubcategoriesCOMMENT
LOW⚡.claude/skills/cts-triage/SKILL.md42## Step 3: Run Each SubcategoryCOMMENT
LOW.claude/skills/cts-triage/SKILL.md56## Step 4: Analyze Failure PatternsCOMMENT
LOW.claude/skills/cts-triage/SKILL.md69## Step 5: Examine Specific FailuresCOMMENT
LOW.claude/skills/cts-triage/SKILL.md84## Step 6: Check CTS Test SourceCOMMENT
LOW.claude/skills/cts-triage/SKILL.md99## Step 7: Categorize IssuesCOMMENT
LOW.claude/skills/cts-triage/SKILL.md126## Step 8: Identify Root CausesCOMMENT
LOW.claude/skills/cts-triage/SKILL.md152## Step 9: Implement FixesCOMMENT
LOW.claude/skills/cts-triage/SKILL.md163## Step 10: Document FindingsCOMMENT
LOW.claude/skills/cts-triage/SKILL.md217## Step 11: Update CTS Result ListsCOMMENT
LOW.claude/skills/cts-triage/SKILL.md244## Step 12: Verify and BuildCOMMENT
Hallucination Indicators4 hits · 40 pts
SeverityFileLineSnippetContext
CRITICALwgpu-hal/src/metal/command.rs1356 while self.state.stage_infos.ms.work_group_memory_sizes.len()CODE
CRITICALwgpu-hal/src/metal/command.rs1359 self.state.stage_infos.ms.work_group_memory_sizes.push(0);CODE
CRITICALwgpu-core/src/command/render.rs3290 if state.pass.base.device.indirect_validation.is_some()CODE
CRITICALwgpu-core/src/command/render.rs3547 let bundle = state.pass.base.tracker.bundles.insert_single(bundle);CODE
AI Slop Vocabulary8 hits · 24 pts
SeverityFileLineSnippetContext
MEDIUMwgpu-hal/Cargo.toml50# The interaction of features between wgpu-core and wgpu-hal is a bit nuanced to getCOMMENT
MEDIUMwgpu-hal/src/auxil/dyn_lib.rs25 _ => crate::DeviceError::Unexpected, // could be unreachable!() but we prefer to be more robustCODE
MEDIUMnaga/src/proc/index.rs79 /// Some graphics hardware provides "robust buffer access", a feature thatCOMMENT
MEDIUMnaga/src/proc/overloads/mod.rs165 /// Essentially, if any one of the arguments is not a constant expression,COMMENT
MEDIUMwgpu/Cargo.toml137#! The following features facilitate integration with third-party supporting libraries.COMMENT
MEDIUM…u/src/documentation/extensions/cooperative_matrices.rs459## Notes and best practicesCOMMENT
MEDIUM⚡wgpu-core/Cargo.toml121#! The following features facilitate integration with third-party supporting libraries.COMMENT
MEDIUMwgpu-core/src/pipeline_cache.rs169 /// We assume that your cache storage system will be relatively robust, and soCOMMENT
Verbosity Indicators3 hits · 6 pts
SeverityFileLineSnippetContext
LOW⚡wgpu-hal/src/dx12/device_creation.rs72 // Step 1: Get ID3D12SDKConfiguration1 via D3D12GetInterfaceCOMMENT
LOW⚡wgpu-hal/src/dx12/device_creation.rs77 // Step 2: Create device factory with the specified SDK version and pathCOMMENT
LOWwgpu-hal/src/vulkan/sampler.rs122 // We need to check if we can create more samplers.COMMENT
Example Usage Blocks2 hits · 3 pts
SeverityFileLineSnippetContext
LOWnaga/src/proc/constant_evaluator.rs453/// Example usage:COMMENT
LOWnaga/src/front/glsl/mod.rs143/// # Example usageCOMMENT
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWcts_runner/src/bootstrap.js295 function DOMExceptionOperationError(msg) {CODE
LOWcts_runner/src/bootstrap.js307 function DOMExceptionInvalidCharacterError(msg) {CODE