AI Slop Code Risk Monitor

dtolnay/cxx

SlopCodeMonitor badge for dtolnay/cxx Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Safe interop between Rust and C++

2.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for dtolnay/cxx, a Rust project with 6,856 GitHub stars. SynthScan examined 31,166 lines of code across 299 source files, recording 74 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 2.4 (Low 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.

2.4
Adjusted Signal
2.4
Raw Pattern Score
100%
Time Factor
2026-10-26
Last Push
6.9K
Stars
Rust
Language
31.2K
Lines of Code
299
Files
74
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

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

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 11.2/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 74 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 11.2/100 · LOW

Which changes need focused human review? 74 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 0MEDIUM 0LOW 74

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 74 distinct pattern matches across 1 syntactic category. 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 Block74 hits · 74 pts
SeverityFileLineSnippetContext
LOWbridge/lib/src/lib.rs1//! The CXX code generator for constructing and compiling C++ code.COMMENT
LOWbridge/src/write.rs541 out.next_section();COMMENT
LOWbridge/src/write.rs561 //COMMENT
LOWbridge/src/mod.rs41/// #COMMENT
LOWbridge/src/builtin/alignmax.h1#pragma onceCOMMENT
LOWinclude/cxx.h1#pragma onceCOMMENT
LOWinclude/cxx.h461COMMENT
LOWtests/cpp_ui_tests.rs21 "include.h",COMMENT
LOWtests/cpp_compile/mod.rs21 /// Path to the `.cc` file (in `temp_dir`) that is generated by theCOMMENT
LOWtests/cpp_compile/mod.rs61 temp_dir,COMMENT
LOWtests/cpp_compile/mod.rs81 ///COMMENT
LOWtests/cpp_compile/mod.rs161 ///COMMENT
LOWmacro/src/expand.rs1681 #cfgCOMMENT
LOWbook/src/concepts.md21 language.COMMENT
LOWbook/src/concepts.md41# unsafe extern "C++" {COMMENT
LOWbook/src/tutorial.md301# fn next_chunk(buf: &mut MultiBuf) -> &[u8];COMMENT
LOWbook/src/tutorial.md381COMMENT
LOWbook/src/tutorial.md401# unsafe extern "C++" {COMMENT
LOWbook/src/tutorial.md521# fn next_chunk(buf: &mut MultiBuf) -> &[u8];COMMENT
LOWsyntax/mangle.rs1// Mangled symbol arrangements:COMMENT
LOWsyntax/mangle.rs21// - cxxbridge1$unique_ptr$std$vector$u8$dropCOMMENT
LOWsyntax/mangle.rs41// pattern: {NAMESPACE...} $ {CXXBRIDGE} $ {CXXVERSION} $ {TYPE} $ operator $ {NAME}COMMENT
LOWsyntax/attrs.rs1use crate::syntax::cfg::CfgExpr;COMMENT
LOWsyntax/instantiate.rs21 ///COMMENT
LOWsrc/lib.rs1//! [![github]](https://github.com/dtolnay/cxx) [![crates-io]](https://crates.io/crates/cxx) [![docs-rs]](httpCOMMENT
LOWsrc/lib.rs21//! *Compiler support: requires rustc 1.88+ and c++11 or newer*<br>COMMENT
LOWsrc/lib.rs41//! If everything checks out statically, then CXX uses a pair of code generatorsCOMMENT
LOWsrc/lib.rs61//! string from C++, its `size()` member function calls Rust's `len()`.COMMENT
LOWsrc/lib.rs81//! // Any shared structs, whose fields will be visible to both languages.COMMENT
LOWsrc/lib.rs101//!COMMENT
LOWsrc/lib.rs121//! ```COMMENT
LOWsrc/lib.rs141//!COMMENT
LOWsrc/lib.rs161//! type depending on your use case.COMMENT
LOWsrc/lib.rs181//! Your function implementations themselves, whether in C++ or Rust, *do not*COMMENT
LOWsrc/lib.rs201//! replacement for the concept of `extern "C"` signatures as we know them,COMMENT
LOWsrc/lib.rs221//! of your FFI that is straightforward and doing the remaining few oddballCOMMENT
LOWsrc/lib.rs241//! ```tomlCOMMENT
LOWsrc/lib.rs261//!COMMENT
LOWsrc/lib.rs281//!COMMENT
LOWsrc/lib.rs301//! may contain internal pointers that would be screwed up by Rust's moveCOMMENT
LOWsrc/lib.rs321//! <br>COMMENT
LOWsrc/lib.rs341//! <tr><td><a href="struct.CxxVector.html">CxxVector&lt;T&gt;</a></td><td>std::vector&lt;T&gt;</td><td><sup><i>cannot bCOMMENT
LOWsrc/cxx_string.rs21 fn string_init(this: &mut MaybeUninit<CxxString>, ptr: *const u8, len: usize);COMMENT
LOWsrc/cxx_string.rs41/// macro, in Rust code we can never obtain a `CxxString` by value. C++'s stringCOMMENT
LOWsrc/cxx_string.rs61/// ```COMMENT
LOWsrc/cxx_string.rs101 /// [`let_cxx_string!`] macro.COMMENT
LOWsrc/cxx_string.rs121 self.len() == 0COMMENT
LOWsrc/cxx_string.rs141 ///COMMENT
LOWsrc/cxx_string.rs161COMMENT
LOWsrc/cxx_string.rs181 ///COMMENT
LOWsrc/cxx_string.rs201 /// **The meaning of the argument is not the same asCOMMENT
LOWsrc/shared_ptr.rs21/// **WARNING:** Unlike Rust's `Arc<T>`, a C++ shared pointer manipulatesCOMMENT
LOWsrc/shared_ptr.rs81 shared_ptr.assume_init()COMMENT
LOWsrc/shared_ptr.rs101 /// Panics if `T` is an incomplete type (including `void`) or is notCOMMENT
LOWsrc/shared_ptr.rs121 ///COMMENT
LOWsrc/shared_ptr.rs141 ///COMMENT
LOWsrc/shared_ptr.rs161 /// # PanicsCOMMENT
LOWsrc/shared_ptr.rs361///COMMENT
LOWsrc/cxx_vector.rs41 /// Constructs a new heap allocated vector, wrapped by UniquePtr.COMMENT
LOWsrc/cxx_vector.rs101 /// This is generally not recommended, use with caution! Calling this methodCOMMENT
14 more matches not shown…