AI Slop Code Risk Monitor

cloudflare/workers-rs

SlopCodeMonitor badge for cloudflare/workers-rs Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Write Cloudflare Workers in 100% Rust via WebAssembly

2.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for cloudflare/workers-rs, a Rust project with 3,767 GitHub stars. SynthScan examined 34,846 lines of code across 378 source files, recording 91 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.7 (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.7
Adjusted Signal
2.7
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
3.8K
Stars
Rust
Language
34.8K
Lines of Code
378
Files
91
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 12.6/100 · LOW

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

Which changes need focused human review? 91 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 91

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 91 distinct pattern matches across 4 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 Block84 hits · 84 pts
SeverityFileLineSnippetContext
LOWtsconfig.json1{COMMENT
LOWtsconfig.json21 // "jsxImportSource": "", /* Specify module specifier used to import the JSX factory funcCOMMENT
LOWtsconfig.json41 // "customConditions": [], /* Conditions to set in addition to the resolver-specific defauCOMMENT
LOWtsconfig.json61 // "importHelpers": true, /* Allow importing helper functions from tslib once per projectCOMMENT
LOWtsconfig.json81 // "preserveSymlinks": true, /* Disable resolving symlinks to their realpath. This correlateCOMMENT
LOWworker-build/src/emoji.rs1//! Emoji constants used by `worker-build`.COMMENT
LOWworker-build/src/build_lock.rs1//! Build lock using a `.tmp` staging directory with mtime-based heartbeat.COMMENT
LOWtest/src/router.rs21};COMMENT
LOWworker-macros/src/lib.rs1mod async_export;COMMENT
LOWworker-macros/src/lib.rs21///COMMENT
LOWworker-macros/src/lib.rs41/// By default all durable object events are enabled.COMMENT
LOWworker-macros/src/lib.rs61 .into()COMMENT
LOWworker-macros/src/lib.rs81///COMMENT
LOWworker-macros/src/lib.rs101/// ```COMMENT
LOWworker-macros/src/lib.rs121pub fn event(attr: TokenStream, item: TokenStream) -> TokenStream {COMMENT
LOWworker-macros/src/async_export.rs1use proc_macro2::TokenStream;COMMENT
LOWworker-sys/src/types/email.rs1// Generated by ts-gen. Do not edit.COMMENT
LOWworker-sys/src/types/email.rs41 }COMMENT
LOWworker-sys/src/types/email.rs61 #[doc = " Returns: void"]COMMENT
LOWworker-sys/src/types/durable_object/sql_storage.rs1use js_sys::{Array, Iterator as JsIterator, Object};COMMENT
LOWworker-sys/src/types/durable_object/container.rs1use js_sys::{Object, Promise};COMMENT
LOW.github/changeset-version.js1const { execSync } = require("node:child_process");COMMENT
LOWtemplates/leptos/Cargo.toml81# Optional. Can be over-ridden with the command line parameter --bin-featuresCOMMENT
LOWtemplates/leptos/src/main.rs1pub fn main() {COMMENT
LOWworker/src/response.rs221COMMENT
LOWworker/src/response.rs381 Ok(self)COMMENT
LOWworker/src/cache.rs21/// - `Cache-Tag`COMMENT
LOWworker/src/cache.rs61 }COMMENT
LOWworker/src/cache.rs81 .put_with_request(&request.try_into()?, &response.into()),COMMENT
LOWworker/src/send.rs1//! This module provides utilities for working with JavaScript typesCOMMENT
LOWworker/src/ai.rs41 /// The returned [`ByteStream`] implements [`Stream`](futures_util::Stream) and can be:COMMENT
LOWworker/src/ai.rs61 /// async fn generate_image(env: &Env) -> Result<Response> {COMMENT
LOWworker/src/ai.rs81 ///COMMENT
LOWworker/src/ai.rs101 ///COMMENT
LOWworker/src/error.rs41 ///COMMENT
LOWworker/src/error.rs61 /// Currently only produced by the email forwarder. May be produced by otherCOMMENT
LOWworker/src/error.rs321impl Error {COMMENT
LOWworker/src/lib.rs1#![allow(clippy::new_without_default)]COMMENT
LOWworker/src/lib.rs21//! #[event(queue)]COMMENT
LOWworker/src/lib.rs41//! The end result is being able to use frameworks like `axum` directly (see [example](./examples/axum)):COMMENT
LOWworker/src/lib.rs61//!COMMENT
LOWworker/src/lib.rs81//! });COMMENT
LOWworker/src/lib.rs101//! # }COMMENT
LOWworker/src/lib.rs121//!COMMENT
LOWworker/src/lib.rs141//! [example](https://github.com/cloudflare/workers-rs/tree/main/examples/rpc-server).COMMENT
LOWworker/src/queue.rs581 }COMMENT
LOWworker/src/queue.rs621 };COMMENT
LOWworker/src/queue.rs641 ///COMMENT
LOWworker/src/durable.rs1//! Durable Objects provide low-latency coordination and consistent storage for the Workers platform.COMMENT
LOWworker/src/durable.rs221COMMENT
LOWworker/src/durable.rs301 }COMMENT
LOWworker/src/durable.rs321 /// l.set(storage.get("limit").await?.unwrap_or(100));COMMENT
LOWworker/src/durable.rs481 self.put_multiple_raw(values.dyn_into().unwrap()).awaitCOMMENT
LOWworker/src/durable.rs781 #[serde(skip_serializing_if = "Option::is_none")]COMMENT
LOWworker/src/analytics_engine.rs141 /// returns: AnalyticsEngineDataPointBuilderCOMMENT
LOWworker/src/analytics_engine.rs161 /// Adds a numeric value to the end of the array of doubles.COMMENT
LOWworker/src/analytics_engine.rs181 self.doubles.push(&JsValue::from_f64(double.into()));COMMENT
LOWworker/src/analytics_engine.rs201 /// .doubles([1.0, 2.0, 3.0]) // sets double1, double2 and double3COMMENT
LOWworker/src/analytics_engine.rs221 ///COMMENT
LOWworker/src/analytics_engine.rs241 ///COMMENT
24 more matches not shown…
Structural Annotation Overuse3 hits · 4 pts
SeverityFileLineSnippetContext
LOWREADME.md557### Step 1: Add Wrangler and Miniflare to your `devDependencies`COMMENT
LOWREADME.md563### Step 2: Build your worker before running the testsCOMMENT
LOWREADME.md575### Step 3: Configure your Miniflare instance in your JavaScript / TypeScript testsCOMMENT
Example Usage Blocks3 hits · 4 pts
SeverityFileLineSnippetContext
LOWworker/src/response.rs231 /// Example usage:COMMENT
LOWworker/src/response.rs385 /// Example usage:COMMENT
LOWworker/src/crypto.rs9/// Example usage:COMMENT
Overly Generic Function Names1 hit · 1 pts
SeverityFileLineSnippetContext
LOWexamples/kv/worker/worker.js9async function handleRequest() {CODE