AI Slop Code Risk Monitor

foundation/yeti

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

A CSS-first, native, zero-build layout and styling framework for web designers.

0.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for foundation/yeti, a JavaScript project with 29,805 GitHub stars. SynthScan examined 42,257 lines of code across 434 source files, recording 30 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.9 (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.

0.9
Adjusted Signal
0.9
Raw Pattern Score
100%
Time Factor
2026-10-14
Last Push
29.8K
Stars
JavaScript
Language
42.3K
Lines of Code
434
Files
30
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 3.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.3/100 · LOW

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

Agent Over-Engineering Ratio 0.3/100 · LOW

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

PR Review Velocity Impact 4.5/100 · LOW

Which changes need focused human review? 30 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 1HIGH 0MEDIUM 0LOW 29

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 30 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 Block25 hits · 25 pts
SeverityFileLineSnippetContext
LOWplaywright.config.js1import { defineConfig, devices } from 'playwright/test';COMMENT
LOWtest/tools/validate.test.js1001// into attributes.css, so validateVocabulary cannot see it: a pair added toCOMMENT
LOWtest/browser/lib/layout.js1// Shared helpers for the layout fixtures. Every fixture wraps its layout inCOMMENT
LOWbin/shots.js1#!/usr/bin/env nodeCOMMENT
LOWbin/gen-docs.js41// reference page is table and the widest of them do not fit a phone. TheCOMMENT
LOWbin/gen-docs.js81// The srcdoc value's newlines are encoded, because an attribute cannot spanCOMMENT
LOWbin/gen-docs.js101 // and an example that composes components gets all of their scripts.COMMENT
LOWbin/gen-types.js1#!/usr/bin/env nodeCOMMENT
LOWbin/validate-html.js1#!/usr/bin/env nodeCOMMENT
LOWbin/frozen.js1#!/usr/bin/env nodeCOMMENT
LOWbin/lib/html.js1// Thin wrapper over parse5 for the validator. Examples are HTML fragments,COMMENT
LOWbin/lib/minify-css.js1// dist/yeti.min.css. lightningcss is the one dev dependency whose workCOMMENT
LOWbin/lib/minify-js.js1// dist/yeti.min.js. esbuild minifies the module bundle the way lightningcssCOMMENT
LOWsrc/utilities/enter/enter.js1// Enter: data-once. enter.css gives a `.enter[data-once]` element (and, withCOMMENT
LOWsrc/components/demo/demo.js1// Demo frames. A framed demo carries its example twice, once escaped into theCOMMENT
LOWsrc/components/tabs/tabs.js41}COMMENT
LOWsrc/components/dropdown/hover.js1// Dropdown, opening on hover. Nothing but script can open a popover, so a menuCOMMENT
LOWsrc/components/toc/toc.js1// On-page nav: the link whose heading is topmost in view is the current one.COMMENT
LOWsrc/components/field/range.js1// Range: the filled track and the value readout follow the thumb.COMMENT
LOWsrc/components/field/validate.js1// Form validation: the browser already knows what is wrong with a control andCOMMENT
LOWsrc/components/field/validate.js21// message catalogue: everything it says comes from the platform.COMMENT
LOWsrc/components/carousel/carousel.js1// Carousel dots. The dots are links to slide ids so that the component worksCOMMENT
LOWsrc/components/carousel/carousel.js21 // Only a dot pointing at a slide of its own carousel is ours to handle.COMMENT
LOWsrc/components/dialog/dialog.js1// Dialog: the browser opens it. A button carrying commandfor="<id>" andCOMMENT
LOWsrc/components/dialog/dialog.js21 return event.clientX < box.left || event.clientX > box.right || event.clientY < box.top || event.clientY > box.bottom;COMMENT
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALtest/tools/gen-types.test.js91 const expected = tokensSchema.items.properties.group.enum.map((g) => `'${g}'`).join(' | ');CODE
Hyper-Verbose Identifiers3 hits · 3 pts
SeverityFileLineSnippetContext
LOWbin/validate.js550export function validateAnchorsAndContainers(srcDir) {CODE
LOWbin/validate.js709export function findNestedThresholdClusters(tree, file, lineOffset = 0) {CODE
LOWbin/validate.js726export function findUntrackedGridPlacement(tree, file, lineOffset = 0) {CODE
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWbin/lib/validate-themes.js30const PSEUDO_ELEMENTS = new Set(['selection', 'marker', 'placeholder', 'first-line', 'first-letter']);CODE