AI Slop Code Risk Monitor

nexu-io/html-anything

Name: nexu-io/html-anything — HTML 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).

✨ The agentic HTML editor — your local AI agent writes the HTML, you ship it. 🚀 75 Skills × 9 Surfaces (magazine · deck · poster · XHS / tweet · prototype · data report · Hyperframes) 🛡️ Sandboxed preview · 📤 1-click to WeChat / X / Zhihu / HTML / PNG 🔑 Zero API key — Claude Code / Cursor / Codex / Gemini / Copilot / OpenCode / Qwen / Aider.

0.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nexu-io/html-anything, a HTML project with 9,349 GitHub stars. SynthScan examined 57,038 lines of code across 350 source files, recording 28 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.8 (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.8

Adjusted Signal

0.8

Raw Pattern Score

100%

Time Factor

2026-10-13

Last Push

9.3K

Stars

HTML

Language

57.0K

Lines of Code

350

Files

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

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

Hallucinated Dependency & Supply Chain Risk 1.1/100 · LOW

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

Agent Over-Engineering Ratio 2.4/100 · LOW

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

PR Review Velocity Impact 4.0/100 · LOW

Which changes need focused human review? 28 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 9LOW 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 28 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.

Decorative Section Separators7 hits · 21 pts

Severity	File	Line	Snippet	Context
MEDIUM	next/src/lib/store.ts	591	// ── selectors / hooks for active task ──────────────────────────────	COMMENT
MEDIUM	next/src/lib/templates/loader.ts	89	// ─── frontmatter parser ──────────────────────────────────────────────	COMMENT
MEDIUM	next/src/lib/templates/loader.ts	196	// ─── public surface ──────────────────────────────────────────────────	COMMENT
MEDIUM	cli/src/agents-invoke.ts	63	// ─── argv builder ────────────────────────────────────────────────────	COMMENT
MEDIUM	cli/src/agents-invoke.ts	188	// ─── stdout parser ────────────────────────────────────────────────────	COMMENT
MEDIUM	cli/src/agents-invoke.ts	404	// ─── resolve OpenClaw agent id ────────────────────────────────────────	COMMENT
MEDIUM	cli/src/agents-invoke.ts	438	// ─── main invoke function ─────────────────────────────────────────────	COMMENT

Fake / Example Data12 hits · 12 pts

Severity	File	Line	Snippet	Context
LOW	README.md	369	- Must use the user's real data, no lorem ipsum.	CODE
LOW	CONTRIBUTING.md	84	- Must use the user's real data. No `lorem ipsum`. No invented metrics. No purple gradients.	CODE
LOW	CONTRIBUTING.md	105	4. No `lorem ipsum` anywhere in the example. If the example uses placeholder data, it must be plausibly-real placeho	CODE
LOW	README.zh-CN.md	265	- 必须使用用户提供的真实数据，禁止 lorem ipsum。	CODE
LOW	CONTRIBUTING.zh-CN.md	84	- 必须使用用户提供的真实数据。禁止 `lorem ipsum`、禁止编造指标、禁止紫色渐变。	CODE
LOW	CONTRIBUTING.zh-CN.md	104	4. example 里不许有 `lorem ipsum`。要用占位数据，也得是看起来像真的占位数据。	CODE
LOW	next/src/lib/templates/shared.ts	34	- 必须使用用户提供的真实数据, 不要编造、不要 lorem ipsum、不要 "Your text here"。	CODE
LOW	…t/src/lib/templates/skills/frame-glitch-title/SKILL.md	48	- 严禁 lorem ipsum; 必须用用户的标题 + 副标。	CODE
LOW	…c/lib/templates/skills/deck-guizang-editorial/SKILL.md	48	- 不许: 数据捏造、Lorem ipsum、占位图片 URL。所有图请用纯 CSS / SVG 内联描绘 (色块 + 简笔)。	CODE
LOW	next/src/lib/templates/skills/mockup-device-3d/SKILL.md	46	- 必须用用户真实数据填充屏幕内容, 严禁 lorem ipsum 或 "Your text here"。	CODE
LOW	…c/lib/templates/skills/deck-open-slide-canvas/SKILL.md	52	- 必须用用户的真实内容; 严禁 lorem ipsum。	CODE
LOW	cli/src/prompt-assemble.ts	33	- 必须使用用户提供的真实数据, 不要编造、不要 lorem ipsum、不要 "Your text here"。	CODE

Hyper-Verbose Identifiers7 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW	next/src/lib/deploy/url-check.ts	40	export function isVercelProtectedResponse(resp: Response, body = ""): boolean {	CODE
LOW	next/src/lib/deploy/url-check.ts	124	export async function waitForReachableDeploymentUrl(	CODE
LOW	next/src/lib/deploy/config.ts	126	export async function readCloudflarePagesConfig(): Promise<DeployConfig> {	CODE
LOW	next/src/lib/deploy/config.ts	180	export async function writeCloudflarePagesConfig(	CODE
LOW	next/src/lib/deploy/config.ts	249	export function publicCloudflarePagesConfig(	CODE
LOW	next/src/lib/deploy/config.ts	262	export function publicDeployConfigForProvider(	CODE
LOW	next/src/lib/deploy/vercel.ts	114	async function disableVercelDeploymentProtection(	CODE

Modern AI Meta-Vocabulary2 hits · 5 pts

Severity	File	Line	Snippet	Context
MEDIUM	next/src/components/formats-gallery.tsx	120	content: `# PDF: agentic-rl-paper.pdf	CODE
MEDIUM	next/src/lib/extract-html.ts	41	// 5. Wrap whatever we got in a minimal scaffold so something renders	COMMENT