AI Slop Code Risk Monitor

epicweb-dev/epic-stack

SlopCodeMonitor badge for epicweb-dev/epic-stack Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

This is a Full Stack app starter with the foundational things setup and configured for you to hit the ground running on your next EPIC idea.

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for epicweb-dev/epic-stack, a TypeScript project with 5,544 GitHub stars. SynthScan examined 48,224 lines of code across 269 source files, recording 19 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.5
Adjusted Signal
0.5
Raw Pattern Score
100%
Time Factor
2026-10-25
Last Push
5.5K
Stars
TypeScript
Language
48.2K
Lines of Code
269
Files
19
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 2.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 0.9/100 · LOW

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

PR Review Velocity Impact 1.9/100 · LOW

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

Hyper-Verbose Identifiers9 hits · 9 pts
SeverityFileLineSnippetContext
LOWapp/utils/permissions.server.ts6export async function requireUserWithPermission(CODE
LOWapp/utils/headers.server.ts75export function getConservativeCacheControl(CODE
LOWapp/utils/sentry-event-filters.ts12export function isExpectedReactRouterErrorMessage(message: string): boolean {CODE
LOWapp/routes/settings/profile/passkeys.tsx98 async function handlePasskeyRegistration() {CODE
LOWapp/routes/_auth/forgot-password.test.ts30function createForgotPasswordRequest(CODE
LOWapp/routes/_auth/verify.server.ts58export async function requireRecentVerification(request: Request) {CODE
LOWapp/routes/_auth/reset-password.tsx26async function requireResetPasswordUsername(request: Request) {CODE
LOWtests/utils.ts14export async function getSessionSetCookieHeader(CODE
LOWtests/playwright-utils.ts37async function getOrInsertUser({CODE
Structural Annotation Overuse4 hits · 9 pts
SeverityFileLineSnippetContext
LOW⚡docs/skills/epic-database/SKILL.md279// Step 1: Widen app (accepts both)COMMENT
LOW⚡docs/skills/epic-database/SKILL.md287// Step 2: Widen db (migration copies data)COMMENT
LOW⚡docs/skills/epic-database/SKILL.md293// Step 3: Narrow app (only uses new fields)COMMENT
LOW⚡docs/skills/epic-database/SKILL.md296// Step 4: Narrow db (removes old field)COMMENT
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtypes/env.env.d.ts1/// <reference types="vite/client" />COMMENT
LOWtypes/deps.d.ts1// This module should contain type definitions for modules which do not haveCOMMENT
LOWdocs/skills/epic-deployment/SKILL.md301COMMENT
Fake / Example Data2 hits · 2 pts
SeverityFileLineSnippetContext
LOWdocs/skills/epic-database/SKILL.md453 email: 'user@example.com',CODE
LOWdocs/skills/epic-database/SKILL.md766 email: 'user@example.com',CODE
Overly Generic Function Names1 hit · 1 pts
SeverityFileLineSnippetContext
LOWapp/entry.server.tsx30export default async function handleRequest(...args: DocRequestArgs) {CODE