AI Slop Code Risk Monitor

Lissy93/dashy

Name: Lissy93/dashy — Vue 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).

🚀 A self-hostable personal dashboard built for you. Includes status-checking, widgets, themes, icon packs, a UI editor and tons more!

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for Lissy93/dashy, a Vue project with 26,879 GitHub stars. SynthScan examined 86,741 lines of code across 473 source files, recording 25 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 0.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.

0.4

Adjusted Signal

0.4

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

26.9K

Stars

Vue

Language

86.7K

Lines of Code

473

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

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

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 1.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 0HIGH 1MEDIUM 1LOW 23

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

Structural Annotation Overuse10 hits · 18 pts

Severity	File	Line	Snippet	Context
LOW⚡	docs/troubleshooting.md	1129	#### Step 1 - Where to open issues	COMMENT
LOW⚡	docs/troubleshooting.md	1133	#### Step 2 - Checking it's not already covered	COMMENT
LOW⚡	docs/troubleshooting.md	1140	#### Step 3 - Describe the Issue	COMMENT
LOW⚡	docs/troubleshooting.md	1147	#### Step 4 - Provide Supporting Info	COMMENT
LOW	docs/troubleshooting.md	1159	#### Step 5 - Fix Released	COMMENT
LOW	docs/development-guides.md	261	### Step 0 - Prerequisites	COMMENT
LOW	docs/development-guides.md	269	### Step 1 - Create Widget	COMMENT
LOW	docs/development-guides.md	323	### Step 2 - Adding Functionality	COMMENT
LOW	docs/development-guides.md	426	### Step 3 - Register	COMMENT
LOW	docs/development-guides.md	439	### Step 4 - Docs	COMMENT

Over-Commented Block5 hits · 5 pts

Severity	File	Line	Snippet	Context
LOW	render.yaml	1	# Render Blueprint https://render.com/docs/blueprint-spec	COMMENT
LOW	.github/zizmor.yml	1	# zizmor config, for the static analysis of our GH Actions workflows	COMMENT
LOW	.github/workflows/tag.yml	1	# Creates a new git tag when a PR is merged, or on manual dispatch	COMMENT
LOW	.github/workflows/docker.yml	1	# Builds and publishes the multi-arch Docker image	COMMENT
LOW	src/styles/user-defined-themes.scss	1	// Put your custom themes here.	COMMENT

Magic Placeholder Names1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	docs/troubleshooting.md	1056	To test your API key, try making a request to `https://api.openweathermap.org/data/2.5/weather?q=London&appid=[your-api-	CODE

Slop Phrases4 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	.github/workflows/close-stale-issues.yml	105	addressed. Don't forget to provide this within the next few days to	CODE
LOW	.github/workflows/close-stale-issues.yml	124	stale-issue-message: Hey @Lissy93 - Don't forget to respond!	CODE
LOW	.github/workflows/close-stale-issues.yml	125	stale-pr-message: Hey @Lissy93 - Don't forget to respond!	CODE
LOW	src/styles/user-defined-themes.scss	2	// Don't forget to also put your theme name into the config	COMMENT

Fake / Example Data4 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	tests/components/livetennis.test.js	46	p2: { id: 9001, name: 'Jane Doe', ranking: null },	CODE
LOW	docs/troubleshooting.md	1188	- `git config --global user.name "John Doe"`	CODE
LOW	src/components/FormElements/Input.vue	16	:placeholder="placeholder"	CODE
LOW	src/components/Widgets/CustomSearch.vue	6	:placeholder="placeholder">	CODE

AI Slop Vocabulary1 hit · 2 pts

Severity	File	Line	Snippet	Context
MEDIUM	.github/workflows/docker.yml	34	contents: read # least-privilege default; jobs elevate as needed	CODE