AI Slop Code Risk Monitor

emotion-js/emotion

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

👩‍🎤 CSS-in-JS library designed for high performance style composition

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for emotion-js/emotion, a JavaScript project with 18,025 GitHub stars. SynthScan examined 43,138 lines of code across 669 source files, recording 21 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.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.

0.7
Adjusted Signal
0.7
Raw Pattern Score
100%
Time Factor
2026-10-23
Last Push
18.0K
Stars
JavaScript
Language
43.1K
Lines of Code
669
Files
21
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 2.5/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.1/100 · LOW

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

Agent Over-Engineering Ratio 1.5/100 · LOW

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

PR Review Velocity Impact 3.6/100 · LOW

Which changes need focused human review? 21 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 1LOW 19

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 21 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.

Hyper-Verbose Identifiers13 hits · 13 pts
SeverityFileLineSnippetContext
LOWscripts/test-utils/src/index.js46export async function disableBrowserEnvTemporarily(fn) {CODE
LOW…ages/babel-plugin/src/utils/transpiled-output-utils.js3export function getTypeScriptMakeTemplateObjectPath(path) {CODE
LOW…ages/babel-plugin/src/utils/transpiled-output-utils.js29export function isTaggedTemplateTranspiledByBabel(path) {CODE
LOWpackages/babel-plugin/src/utils/minify.js84function replacePlaceholdersWithExpressions(CODE
LOWpackages/babel-plugin/src/utils/minify.js123function createRawStringFromTemplateLiteral(CODE
LOWpackages/primitives/src/test-props.js51export function testPickPropsOnPrimitiveComponent(prop /*: string */) {CODE
LOWpackages/primitives/src/test-props.js61export function testPickPropsOnOtherComponent(prop /*: string */) {CODE
LOWpackages/jest/src/create-serializer.js66function getPrettyStylesFromClassNames(CODE
LOWpackages/jest/src/utils.js62function getClassNamesFromTestRenderer(selectors, { props = {} }) {CODE
LOWpackages/jest/src/utils.js84export function unwrapFromPotentialFragment(node) {CODE
LOWpackages/jest/src/utils.js112function getClassNamesFromDOMElement(selectors, node) {CODE
LOWpackages/jest/src/utils.js123export function isEmotionCssPropElementType(val) /*: boolean */ {CODE
LOWpackages/jest/src/utils.js138export function isEmotionCssPropEnzymeElement(val /* : any */) /*: boolean */ {CODE
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICAL…ages/babel-plugin/src/utils/transpiled-output-utils.js16 firstArgPath.node.right.right.callee.name.includes('makeTemplateObject') &&CODE
Over-Commented Block6 hits · 6 pts
SeverityFileLineSnippetContext
LOWpackages/cache/src/stylis-plugins.ts181 // .b /* comm */ {}COMMENT
LOWpackages/cache/src/stylis-plugins.ts201 breakCOMMENT
LOWpackages/is-prop-valid/src/props.js201 // used in amp html for indicating the fallback behaviorCOMMENT
LOWpackages/is-prop-valid/src/props.js221 option: true,COMMENT
LOWpackages/is-prop-valid/src/props.js241 // onfocusoutCOMMENT
LOWsite/next-env.d.ts1/// <reference types="next" />COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMpackages/cache/src/stylis-plugins.ts57 // it's very unlikely for this sequence to actually appear in a different context, so we just leverage this faCOMMENT