AI Slop Code Risk Monitor

joyce677/TrendRadar

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

一键监控今日头条、百度热搜、微博、抖音、知乎、B站等35个平台,智能关键词筛选,自动生成热点分析报告。支持企业微信、飞书、钉钉、Telegram推送,30秒网页部署,1分钟手机通知,无需编程基础。还有文字和图片版api可调用

0.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for joyce677/TrendRadar, a HTML project with 1,903 GitHub stars. SynthScan examined 6,610,816 lines of code across 13652 source files, recording 57 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 0.0 (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.0
Adjusted Signal
0.0
Raw Pattern Score
100%
Time Factor
2026-10-20
Last Push
1.9K
Stars
HTML
Language
6.6M
Lines of Code
13.7K
Files
57
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 0.0/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 0.1/100 · LOW

Which changes need focused human review? 57 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 1MEDIUM 1LOW 55

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

Excessive Try-Catch Wrapping28 hits · 28 pts
SeverityFileLineSnippetContext
MEDIUMmain.py244def parse_version(version_str):CODE
LOW⚡main.py3019 except Exception:CODE
LOWmain.py176 except Exception as e:CODE
LOWmain.py259 except Exception as e:CODE
LOWmain.py322 except Exception as e:CODE
LOWmain.py336 except Exception as e:CODE
LOWmain.py355 except Exception as e:CODE
LOWmain.py419 except Exception as e:CODE
LOWmain.py472 except Exception as e:CODE
LOWmain.py656 except Exception as e:CODE
LOWmain.py2776 except Exception as e:CODE
LOWmain.py2821 except Exception as e:CODE
LOWmain.py2880 except Exception as e:CODE
LOWmain.py2952 except Exception as e:CODE
LOWmain.py3051 except Exception as e:CODE
LOWmain.py3118 except Exception as e:CODE
LOWmain.py3475 except Exception as e:CODE
LOWmain.py3636 except Exception as e:CODE
LOWmain.py3686 except Exception as e:CODE
LOWdocker/manage.py21 except Exception as e:CODE
LOWdocker/manage.py36 except Exception as e:CODE
LOWdocker/manage.py117 except Exception as e:CODE
LOWdocker/manage.py139 except Exception as e:CODE
LOWdocker/manage.py226 except Exception as e:CODE
LOWdocker/manage.py303 except Exception as e:CODE
LOWdocker/manage.py368 except Exception as e:CODE
LOWdocker/manage.py392 except Exception as e:CODE
LOWdocker/manage.py464 except Exception as e:STRING
Deep Nesting20 hits · 12 pts
SeverityFileLineSnippetContext
LOWmain.py488CODE
LOWmain.py538CODE
LOWmain.py592CODE
LOWmain.py662CODE
LOWmain.py706CODE
LOWmain.py779CODE
LOWmain.py925CODE
LOWmain.py965CODE
LOWmain.py1276CODE
LOWmain.py1373CODE
LOWmain.py1547CODE
LOWmain.py2229CODE
LOWmain.py2322CODE
LOWmain.py2826CODE
LOWmain.py2888CODE
LOWmain.py432CODE
LOWmain.py3181CODE
LOWdocker/manage.py40CODE
LOWdocker/manage.py121CODE
LOWdocker/manage.py309CODE
Hyper-Verbose Identifiers7 hits · 6 pts
SeverityFileLineSnippetContext
LOW⚡main.py3009 def _detect_docker_environment(self) -> bool:CODE
LOWmain.py1373def format_title_for_platform(CODE
LOWmain.py2322def split_content_into_batches(CODE
LOWmain.py3122 def _prepare_current_title_info(self, results: Dict, time_info: str) -> Dict:CODE
LOWmain.py3181 def _send_notification_if_needed(CODE
LOWmain.py3300 def _initialize_and_check_config(self) -> None:CODE
LOWmain.py3568def generate_static_api_files(analyzer: "NewsAnalyzer"):CODE
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHdocker/manage.py184except:CODE
Modern Structural Boilerplate1 hit · 2 pts
SeverityFileLineSnippetContext
LOW⚡main.py3026 def _setup_proxy(self) -> None:CODE