AI Slop Code Risk Monitor

asxez/DockerDesktop-CN

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

Docker汉化 Docker中文版 Docker汉化包 DockerDesktop汉化 Docker Windows Docker MAC

3.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for asxez/DockerDesktop-CN, a Python project with 10,217 GitHub stars. SynthScan examined 8,343 lines of code across 25 source files, recording 20 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 3.4 (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.

3.4
Adjusted Signal
3.4
Raw Pattern Score
100%
Time Factor
2026-10-28
Last Push
10.2K
Stars
Python
Language
8.3K
Lines of Code
25
Files
20
Pattern Hits
2026-10-31
Scan Date
0.08
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 8.6/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 6.4/100 · LOW

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

Agent Over-Engineering Ratio 3.5/100 · LOW

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

PR Review Velocity Impact 16.5/100 · LOW

Which changes need focused human review? 20 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 2MEDIUM 0LOW 18

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 20 distinct pattern matches across 6 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.

Cross-Language Confusion2 hits · 10 pts
SeverityFileLineSnippetContext
HIGHtest/test.py54 'children:["The \'",t[0],"\' ",e," is selected for deletion.",i?` ${i}`:null]',CODE
HIGHtest/test.py57 'children:["\'",t[0],"\' ",e," 被选中删除。",i?` ${i}`:null]',CODE
Deep Nesting8 hits · 8 pts
SeverityFileLineSnippetContext
LOWtools/extract_windows_payload.py9CODE
LOWlib/processor.py73CODE
LOWlib/processor.py106CODE
LOWlib/processor.py363CODE
LOWlib/extract.py194CODE
LOWlib/extract.py225CODE
LOWlib/extract.py299CODE
LOWlib/extract.py65CODE
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOWtest/test.py11def test_extract_nested_children():CODE
LOWlib/processor.py260 def update_macos_asar_integrity(asar_path: Path, info_plist_path: Path):CODE
LOWlib/processor.py301 def check_asar_integrity_writable(asar_path: Path, integrity_path: Path):CODE
LOWlib/processor.py324 def check_macos_asar_integrity_writable(asar_path: Path, info_plist_path: Path):CODE
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtest/__init__.py1# -*- coding: utf-8 -*-COMMENT
LOWcommon/__init__.py1# -*- coding: utf-8 -*-COMMENT
LOWlib/__init__.py1# -*- coding: utf-8 -*-COMMENT
Excessive Try-Catch Wrapping2 hits · 2 pts
SeverityFileLineSnippetContext
LOWlib/processor.py130 except Exception as e:CODE
LOWlib/processor.py377 except Exception as e:CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcommon/__init__.py9CODE