AI Slop Code Risk Monitor

ermaozi/get_subscribe

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

✈️ 白嫖免费机场 / 免费VPN -> 自动获取免 clash/v2ray/trojan/sr/ssr 订阅链接,持续更新 | 科学上网 | 翻墙

2.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for ermaozi/get_subscribe, a Python project with 9,415 GitHub stars. SynthScan examined 15,674 lines of code across 20 source files, recording 17 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 2.2 (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.2
Adjusted Signal
2.2
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
9.4K
Stars
Python
Language
15.7K
Lines of Code
20
Files
17
Pattern Hits
2026-10-31
Scan Date
0.05
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 5.6/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 5.0/100 · LOW

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

Agent Over-Engineering Ratio 4.4/100 · LOW

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

PR Review Velocity Impact 8.0/100 · LOW

Which changes need focused human review? 17 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 16

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 17 distinct pattern matches across 5 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.

Hallucination Indicators1 hit · 15 pts
SeverityFileLineSnippetContext
CRITICAL⚡tests/test_health.py38 factory.return_value.__enter__.return_value.connect.assert_called_once_with(('1.1.1.1',443))CODE
Hyper-Verbose Identifiers10 hits · 13 pts
SeverityFileLineSnippetContext
LOW⚡tests/test_subscriptions.py17 def test_real_formats_and_error_pages(self):CODE
LOW⚡tests/test_subscriptions.py27 def test_download_uses_tls_and_skips_invalid_content(self):CODE
LOW⚡tests/test_subscriptions.py36 def test_collection_and_failed_source_keeps_cache(self):CODE
LOWtests/test_subscriptions.py57 def test_merge_deduplicates_and_keeps_groups_resolvable(self):CODE
LOWtests/test_subscriptions.py69 def test_direct_sources_work_when_rss_fails(self):CODE
LOWtests/test_subscriptions.py85 def test_github_empty_history_and_http_errors(self):CODE
LOWtests/test_health.py14 def test_endpoints_and_udp_are_not_misclassified(self):CODE
LOW⚡tests/test_health.py27 def test_private_addresses_are_not_connected(self):CODE
LOW⚡tests/test_health.py34 def test_tcp_success_and_timeout(self):CODE
LOW⚡tests/test_health.py42 def test_classification_is_complete_and_keeps_original(self):CODE
Deep Nesting4 hits · 4 pts
SeverityFileLineSnippetContext
LOWmain.py69CODE
LOWmain.py143CODE
LOWmain.py196CODE
LOWcheck_nodes.py24CODE
AI Structural Patterns1 hit · 1 pts
SeverityFileLineSnippetContext
LOWget_projaec_info.py54CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtests/test_health.py7CODE