AI Slop Code Risk Monitor

liyupi/codefather

Name: liyupi/codefather — TypeScript Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

程序员鱼皮的编程宝典 ⭐️ 2026年最全编程学习路线图！包含Java学习路线、前端学习路线、Python学习路线、C++学习路线、算法学习路线、计算机基础学习路线、AI应用开发学习路线、AI Agent开发学习路线等。提供编程入门教程、AI大模型应用开发教程、RAG开发实战、MCP开发教程、Prompt工程指南、LLM应用开发、技术知识分享、学习资源推荐、项目实战教程、热门面试题、求职经验、简历优化、编程自学指南等内容，适用于所有零基础学编程、学习AI开发、转行程序员、计算机专业学生、求职找工作的同学 💎 编程学习，就来编程导航！

1.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for liyupi/codefather, a TypeScript project with 8,971 GitHub stars. SynthScan examined 199,161 lines of code across 1031 source files, recording 25 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.1 (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.

1.1

Adjusted Signal

1.1

Raw Pattern Score

100%

Time Factor

2026-07-11

Last Push

9.0K

Stars

TypeScript

Language

199.2K

Lines of Code

1.0K

Files

Pattern Hits

2026-10-31

Scan Date

0.01

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.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 4.5/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 3.8/100 · LOW

Which changes need focused human review? 25 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 12HIGH 0MEDIUM 11LOW 2

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 25 distinct pattern matches across 3 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 Indicators12 hits · 180 pts

Severity	File	Line	Snippet	Context
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	247	at org.apache.tomcat.websocket.pojo.PojoMethodMapping.getPathParams(PojoMethodMapping.java:311) ~[tomcat-embed-webso	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	249	at org.apache.tomcat.websocket.server.WsServerContainer.addEndpoint(WsServerContainer.java:130) ~[tomcat-embed-webso	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	250	at org.apache.tomcat.websocket.server.WsServerContainer.addEndpoint(WsServerContainer.java:240) ~[tomcat-embed-webso	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	251	at org.apache.tomcat.websocket.server.WsServerContainer.addEndpoint(WsServerContainer.java:198) ~[tomcat-embed-webso	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	252	at org.springframework.web.socket.server.standard.ServerEndpointExporter.registerEndpoint(ServerEndpointExporter.jav	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	417	java.lang.NullPointerException: Cannot invoke "cn.springdoc.demo.service.UserService.foo()" because "this.userService" i	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	418	at cn.springdoc.demo.channel.EchoChannel.onOpen(EchoChannel.java:54)	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	423	at org.apache.tomcat.websocket.pojo.PojoEndpointBase.doOnOpen(PojoEndpointBase.java:67)	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	424	at org.apache.tomcat.websocket.pojo.PojoEndpointServer.onOpen(PojoEndpointServer.java:46)	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	425	at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.init(WsHttpUpgradeHandler.java:131)	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	428	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)	CODE
CRITICAL⚡	知识碎片/WebSocket 前后端联调使用.md	429	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)	CODE

Modern AI Meta-Vocabulary11 hits · 32 pts

Severity	File	Line	Snippet	Context
MEDIUM	编程分享/编程资源/项目推荐/前端福音，蚂蚁金服 Ant Design 生态一览.md	87	地址：https://scaffold.ant.design	CODE
MEDIUM	学习路线/2026年最新RAG检索增强生成学习路线零基础到精通一条龙（万人收藏⭐️）.md	109	## 阶段 2：RAG 核心概念（7-15 天，仅供参考）	COMMENT
MEDIUM	学习路线/2026年最新RAG检索增强生成学习路线零基础到精通一条龙（万人收藏⭐️）.md	198	## 阶段 3：RAG 技术实现（15-30 天，仅供参考）	COMMENT
MEDIUM	学习路线/2026年最新RAG检索增强生成学习路线零基础到精通一条龙（万人收藏⭐️）.md	275	## 阶段 4：RAG 优化和进阶（10-20 天，仅供参考）	COMMENT
MEDIUM	学习路线/2026年最新RAG检索增强生成学习路线零基础到精通一条龙（万人收藏⭐️）.md	356	## 阶段 5：RAG 评估和测试（5-10 天，仅供参考）	COMMENT
MEDIUM	学习路线/2026年最新RAG检索增强生成学习路线零基础到精通一条龙（万人收藏⭐️）.md	553	### RAG 项目教程	COMMENT
MEDIUM	学习路线/2026年最新LangChain开发学习路线零基础到精通一条龙（万人收藏⭐️）.md	176	## 阶段 3：文档处理和 RAG（15-30 天，仅供参考）	COMMENT
MEDIUM	学习路线/2026年最新SpringAI学习路线零基础到精通一条龙（万人收藏⭐️）.md	203	## 阶段 3：RAG 开发（5-15 天，仅供参考）	COMMENT
MEDIUM	学习路线/2026年最新LangChain4j学习路线零基础到精通一条龙（万人收藏⭐️）.md	177	## 阶段 3：RAG 开发（5-15 天，仅供参考）	COMMENT
MEDIUM	学习路线/2026年最新AI大模型应用开发零基础到精通一条龙（万人收藏⭐️）.md	503	#### RAG（15天）	COMMENT
MEDIUM	学习路线/2026年最新AI大模型应用开发零基础到精通一条龙（万人收藏⭐️）.md	732	#### RAG 项目（7天）	COMMENT

Fake / Example Data2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	…试题/前端热门面试题 200 道/在 Vue 开发过程中需要同时与多个后端人员联调接口时，你会怎么做？.md	75	res.json({ id: 1, name: 'John Doe' });	CODE
LOW	.vuepress/theme/components/AlgoliaSearchBox.vue	10	:placeholder="placeholder"	CODE