AI Slop Code Risk Monitor

fanmingming/live

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

✯ 可直连访问的电视/广播图标库与相关工具项目 ✯ 🔕 永久免费 直连访问 完整开源 不断完善的台标 支持IPv4/IPv6双栈访问 🔕

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for fanmingming/live, a JavaScript project with 28,747 GitHub stars. SynthScan examined 26,138 lines of code across 27 source files, recording 19 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-31
Last Push
28.7K
Stars
JavaScript
Language
26.1K
Lines of Code
27
Files
19
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.4/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 1.9/100 · LOW

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

PR Review Velocity Impact 3.6/100 · LOW

Which changes need focused human review? 19 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 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 19 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 Identifiers10 hits · 10 pts
SeverityFileLineSnippetContext
LOWm3u8/vue.js2270 function extractPropsFromVNodeData (CODE
LOWm3u8/vue.js3037 function createFunctionalComponent (CODE
LOWm3u8/vue.js3078 function cloneAndMarkFunctionalResult (vnode, data, contextVm, options, renderContext) {CODE
LOWm3u8/vue.js3274 function createComponentInstanceForVnode (CODE
LOWm3u8/vue.js5029 function resolveConstructorOptions (Ctor) {CODE
LOWm3u8/vue.js6126 function removeAndInvokeRemoveHook (vnode, rm) {CODE
LOWm3u8/vue.js7095 function getAndRemoveAttr (CODE
LOWm3u8/vue.js7116 function getAndRemoveAttrByRegex (CODE
LOWm3u8/vue.js10707 function isDirectChildOfTemplateFor (node) {CODE
LOWm3u8/vue.js11634 function createCompileToFunctionFn (compile) {CODE
Over-Commented Block6 hits · 6 pts
SeverityFileLineSnippetContext
LOWm3u8/mux-mp4.js2221 pes.packetLength = 6 + ((payload[4] << 8) | payload[5]);COMMENT
LOWm3u8/mux-mp4.js5401 return;COMMENT
LOWm3u8/mux-mp4.js5421 // throw away all the frames between the start of the fragmentCOMMENT
LOWm3u8/vue.js1921 // (e.g. #6813, out-in transitions).COMMENT
LOWm3u8/vue.js4241 circular = {};COMMENT
LOWm3u8/serviceworker.js1// Service workers 本质上充当 Web 应用程序、浏览器与网络(可用时)之间的代理服务器。COMMENT
Overly Generic Function Names2 hits · 2 pts
SeverityFileLineSnippetContext
LOWm3u8/vue.js4734 function getData (data, vm) {CODE
LOWworker/radio.js4async function handleRequest(request) {CODE
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWm3u8/vue.js6761 key === 'placeholder' && value !== '' && !el.__iephCODE