AI Slop Code Risk Monitor

Michael-A-Kuykendall/shimmy

Name: Michael-A-Kuykendall/shimmy — Rust Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

⚡ Pure-Rust WebGPU inference engine — OpenAI-API compatible, GGUF native, runs on any GPU. No Python. No llama.cpp. Single binary.

2.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Michael-A-Kuykendall/shimmy, a Rust project with 6,004 GitHub stars. SynthScan examined 32,817 lines of code across 152 source files, recording 51 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 2.6 (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.6

Adjusted Signal

2.6

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

6.0K

Stars

Rust

Language

32.8K

Lines of Code

152

Files

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 10.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 2.4/100 · LOW

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

PR Review Velocity Impact 10.2/100 · LOW

Which changes need focused human review? 51 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 10LOW 41

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 51 distinct pattern matches across 9 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.

Structural Annotation Overuse11 hits · 21 pts

Severity	File	Line	Snippet	Context
LOW	DEVELOPERS.md	46	### Step 1: Specify Your Feature (`/specify`)	COMMENT
LOW	DEVELOPERS.md	70	### Step 2: Plan Implementation (`/plan`)	COMMENT
LOW	DEVELOPERS.md	81	### Step 3: Break Into Tasks (`/tasks`)	COMMENT
LOW	docs/MODEL_EXPANSION.md	96	### Step 1: Add the type to the enum	COMMENT
LOW⚡	docs/MODEL_EXPANSION.md	117	### Step 2: Write the dequant shader	COMMENT
LOW⚡	docs/MODEL_EXPANSION.md	123	### Step 3: Wire into the dispatch	COMMENT
LOW⚡	docs/MODEL_EXPANSION.md	128	### Step 4: Validate	COMMENT
LOW	docs/MODEL_EXPANSION.md	152	### Step 1: Add the variant	COMMENT
LOW⚡	docs/MODEL_EXPANSION.md	167	### Step 2: Map the hyperparameter keys	COMMENT
LOW⚡	docs/MODEL_EXPANSION.md	173	### Step 3: Map the weight tensor names	COMMENT
LOW⚡	docs/MODEL_EXPANSION.md	179	### Step 4: Handle architecture-specific ops	COMMENT

Redundant / Tautological Comments11 hits · 16 pts

Severity	File	Line	Snippet	Context
LOW	scripts/setup-precommit.sh	9	# Check if pre-commit is installed	COMMENT
LOW	scripts/dry-run-release.sh	175	# Check if CUDA Toolkit is available for documentation build	COMMENT
LOW	scripts/dry-run-release.sh	214	# Check if all gates passed	COMMENT
LOW	scripts/setup-branch-protection.sh	8	# Check if gh CLI is available	COMMENT
LOW	scripts/setup-branch-protection.sh	15	# Check if authenticated	COMMENT
LOW	scripts/configure-github-protection.sh	8	# Check if gh CLI is available	COMMENT
LOW	scripts/configure-github-protection.sh	16	# Check if authenticated	COMMENT
LOW	scripts/benchmark.sh	57	# Check if Shimmy is running	COMMENT
LOW	scripts/update-changelog.sh	10	# Check if version provided	COMMENT
LOW	scripts/coverage.sh	54	# Display results	COMMENT
LOW	scripts/coverage.sh	67	# Check if meets our 95% standard	COMMENT

Over-Commented Block16 hits · 16 pts

Severity	File	Line	Snippet	Context
LOW	deny.toml	1	# This template contains all of the possible sections and their default values	COMMENT
LOW	deny.toml	21	# `target_family = "unix"` configuration, that only having windows targets in	COMMENT
LOW	deny.toml	41	# be toggled off if true, if you want to conditionally enable `--all-features` it	COMMENT
LOW	deny.toml	61	# More documentation for the advisories section can be found here:	COMMENT
LOW	deny.toml	101	"Zlib",	COMMENT
LOW	deny.toml	121	#[[licenses.clarify]]	COMMENT
LOW	deny.toml	141	ignore = false	COMMENT
LOW	deny.toml	161	# * all - Both lowest-version and simplest-path are used	COMMENT
LOW	deny.toml	181	# is a direct dependency of the otherwise banned crate	COMMENT
LOW	deny.toml	201	# "tokio-rustls",	COMMENT
LOW	.pre-commit-config.yaml	41	# They run automatically on:	COMMENT
LOW	tests/gguf_routing.rs	1	//! `gguf_routing` — the offline "screen test" for template routing.	COMMENT
LOW	src/prompt_render.rs	61	}	COMMENT
LOW	src/cli.rs	101	#[arg(long, default_value = "none")]	COMMENT
LOW	src/openai_compat/types.rs	81	#[derive(Debug, Deserialize)]	COMMENT
LOW	src/util/memory.rs	21	}	COMMENT

Decorative Section Separators5 hits · 15 pts

Severity	File	Line	Snippet	Context
MEDIUM	src/prompt_render.rs	451	// ── decide() — the single render-decision point ─────────────────────────	COMMENT
MEDIUM	src/prompt_render.rs	506	// ── completion no-template -> RAW (base models) ─────────────────────────	COMMENT
MEDIUM	src/prompt_render.rs	524	// ── Gemma family fallback ───────────────────────────────────────────────	COMMENT
MEDIUM	src/openai_compat/mod.rs	1220	// ── penalty mapping ──────────────────────────────────────────────────────	COMMENT
MEDIUM	src/openai_compat/mod.rs	1260	// ── input validation ─────────────────────────────────────────────────────	COMMENT

AI Slop Vocabulary3 hits · 9 pts

Severity	File	Line	Snippet	Context
MEDIUM	scripts/install-hooks.sh	78	# Install pre-push hook (more comprehensive)	COMMENT
MEDIUM	scripts/coverage.sh	3	# Generates comprehensive coverage reports with all feature combinations	COMMENT
MEDIUM	scripts/coverage.sh	21	# Generate coverage with all features (most comprehensive)	COMMENT

Modern AI Meta-Vocabulary2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	docs/FAQ.md	68	### Can I extend the context window beyond what the model was trained on?	COMMENT
MEDIUM	docs/EXTENDED_CONTEXT.md	167	# Set context window at server start	COMMENT

Deep Nesting1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	scripts/smoke_text.py	31		CODE

Excessive Try-Catch Wrapping1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	templates/frameworks/fastapi/main.py	113	except Exception as e:	CODE

Unused Imports1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	templates/frameworks/fastapi/main.py	4		CODE