AI Slop Code RIsk Monitor

Rust-GPU/rust-cuda

Ecosystem of libraries and tools for writing and executing fast GPU code fully in Rust.

6.7 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for Rust-GPU/rust-cuda, a Rust project with 5,406 GitHub stars. SynthScan examined 102,053 lines of code across 481 source files, recording 688 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 6.7 (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.

6.7
Adjusted Signal
6.7
Raw Pattern Score
100%
Time Factor
2026-09-30
Last Push
5.4K
Stars
Rust
Language
102.1K
Lines of Code
481
Files
688
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 28.3/100 · MEDIUM

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 29.2/100 · MEDIUM

Which changes need focused human review? 688 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 0HIGH 2MEDIUM 4LOW 682

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 688 distinct pattern matches across 3 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 Block682 hits · 653 pts
SeverityFileLineSnippetContext
LOWCargo.toml21 # OPTIX_DISABLED: These crates that rely on OptiX are disabled because OptiX is less importantCOMMENT
LOWguide/src/guide/getting_started.md261 // - The first two parameters between the triple angle brackets specify 1COMMENT
LOWcrates/nvvm/src/lib.rs61}COMMENT
LOWcrates/nvvm/src/lib.rs261///COMMENT
LOWcrates/nvvm/src/lib.rs281///COMMENT
LOWcrates/nvvm/src/lib.rs501 Self::Compute121 => "compute_121",COMMENT
LOWcrates/nvvm/src/lib.rs521 /// let features = Compute61.all_target_features();COMMENT
LOWcrates/cuda_builder/src/lib.rs61 path_to_crate: PathBuf,COMMENT
LOWcrates/cuda_builder/src/lib.rs81 /// you are using recent features such as tensor cores (which need at least 7.x).COMMENT
LOWcrates/cuda_builder/src/lib.rs101 /// forward-compatible within same major version (10.0, 10.3, etc.) but NOT acrossCOMMENT
LOWcrates/cuda_builder/src/lib.rs121 /// // Code that requires compute capability 6.1+ will be emitted because it matchesCOMMENT
LOWcrates/cuda_builder/src/lib.rs141 pub ftz: bool,COMMENT
LOWcrates/cuda_builder/src/lib.rs161 /// Code compiled with this option should always work under CUDA, but it might not be the most efficient or practicaCOMMENT
LOWcrates/cuda_builder/src/lib.rs181 /// The default is `false`, which places all statics in global memory. This avoidsCOMMENT
LOWcrates/cuda_builder/src/lib.rs301 self.ptx_file_copy_path = Some(path.as_ref().to_path_buf());COMMENT
LOWcrates/cuda_builder/src/lib.rs321 /// exposes the option to automatically override any calls to libm functions with calls to libdevice functions.COMMENT
LOWcrates/ptx/src/types.rs201#[derive(Debug, Clone, PartialEq)]COMMENT
LOWcrates/cuda_std_macros/src/lib.rs1use proc_macro::TokenStream;COMMENT
LOWcrates/cuda_std_macros/src/lib.rs141/// `local`.COMMENT
LOWcrates/cuda_std_macros/src/lib.rs161/// Shared memory usage is fundamentally unsafe and much of the burden of correctness is on theCOMMENT
LOWcrates/cuda_std_macros/src/lib.rs181/// pub unsafe fn reverse_array(d: *mut u32, n: usize) {COMMENT
LOWcrates/blastoff/src/level1.rs61 ///COMMENT
LOWcrates/blastoff/src/level1.rs121 ///COMMENT
LOWcrates/blastoff/src/level1.rs181 .to_result()?)COMMENT
LOWcrates/blastoff/src/level1.rs201 /// # let stream = Stream::new(StreamFlags::DEFAULT, None)?;COMMENT
LOWcrates/blastoff/src/level1.rs261 /// Panics if `x` or `y` are not large enough for the requested amount of elements.COMMENT
LOWcrates/blastoff/src/level1.rs321 result.as_device_ptr().as_mut_ptr(),COMMENT
LOWcrates/blastoff/src/level1.rs341 /// # let _a = cust::quick_init()?;COMMENT
LOWcrates/blastoff/src/level1.rs501 /// # PanicsCOMMENT
LOWcrates/blastoff/src/level1.rs581 /// -s & cCOMMENT
LOWcrates/blastoff/src/level1.rs601 /// $$COMMENT
LOWcrates/blastoff/src/level1.rs621 /// let s = DeviceBox::new(&0.0)?;COMMENT
LOWcrates/blastoff/src/level3.rs61COMMENT
LOWcrates/blastoff/src/context.rs21 /// also use tensor cores when possible.COMMENT
LOWcrates/blastoff/src/context.rs41/// so we do not expose this functionality. Instead, you should create a context for every thread (as the cuBLAS docs reCOMMENT
LOWcrates/blastoff/src/context.rs61/// - [Dot Product <span style="float:right;">`dot`</span>](CublasContext::dot)COMMENT
LOWcrates/blastoff/src/context.rs81 ///COMMENT
LOWcrates/blastoff/src/context.rs161 }COMMENT
LOWcrates/blastoff/src/context.rs201 /// Returns `false` unless previously explicitly set to `true`.COMMENT
LOWcrates/blastoff/src/context.rs221 cublas_sys::cublasAtomicsMode_t::CUBLAS_ATOMICS_NOT_ALLOWED => false,COMMENT
LOWcrates/blastoff/src/context.rs241 Ok(cublas_sys::cublasSetMathMode(COMMENT
LOWcrates/blastoff/src/context.rs261 /// # }COMMENT
LOWcrates/blastoff/src/context.rs281 /// ```COMMENT
LOWcrates/optix/examples/common/gdt/CMakeLists.txt1# ======================================================================== #COMMENT
LOWcrates/optix/examples/common/gdt/gdt/gdt.cpp1// ======================================================================== //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/gdt.h1// ======================================================================== //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/gdt.h21#include <stdexcept>COMMENT
LOWcrates/optix/examples/common/gdt/gdt/gdt.h41 #endifCOMMENT
LOWcrates/optix/examples/common/gdt/gdt/gdt.h61#endifCOMMENT
LOWcrates/optix/examples/common/gdt/gdt/gdt.h81COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/box.h1// ======================================================================== //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/vec.h1// ======================================================================== //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/AffineSpace.h1// ======================================================================== //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/AffineSpace.h21// //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/AffineSpace.h141 // const vec_t<S,3,A> p4(b.upper.x,b.lower.y,b.lower.z); dst.extend(xfmPoint(m,p4));COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/LinearSpace.h1// ======================================================================== //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/LinearSpace.h21// //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/Quaternion.h1// ======================================================================== //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/Quaternion.h21// //COMMENT
LOWcrates/optix/examples/common/gdt/gdt/math/constants.h1// ======================================================================== //COMMENT
622 more matches not shown…
Synthetic Comment Markers2 hits · 15 pts
SeverityFileLineSnippetContext
HIGHcrates/blastoff/src/context.rs20 /// with at least the same number of mantissa and exponent bits as requested. WillCOMMENT
HIGHcrates/optix/src/context.rs242 /// * 3 - warning: Hints that OptiX might not behave exactly as requested by theCOMMENT
AI Slop Vocabulary4 hits · 12 pts
SeverityFileLineSnippetContext
MEDIUMcrates/rustc_codegen_nvvm/src/intrinsic.rs747 // targets that support it we can typically leverage inline assembly to doCOMMENT
MEDIUMcrates/cudnn/src/lib.rs64//! original cuDNN enumerated data types and instead opted to leverage Rust's generics. InCOMMENT
MEDIUMcrates/cudnn/src/math_type.rs12 /// down conversion on tensors in order to utilize Tensor Cores.COMMENT
MEDIUMcrates/cudnn/src/math_type.rs15 /// conversion on tensors in order to utilize Tensor Cores.COMMENT