AI Slop Code Risk Monitor

koodo-reader/koodo-reader

SlopCodeMonitor badge for koodo-reader/koodo-reader Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

A modern ebook manager and reader with sync and backup capacities for Windows, macOS, Linux, Android, iOS and Web

0.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for koodo-reader/koodo-reader, a JavaScript project with 28,681 GitHub stars. SynthScan examined 163,383 lines of code across 589 source files, recording 42 pattern matches distributed across 8 syntactic categories. The legacy adjusted pattern signal is 0.6 (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.6
Adjusted Signal
0.6
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
28.7K
Stars
JavaScript
Language
163.4K
Lines of Code
589
Files
42
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.6/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 2.1/100 · LOW

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

PR Review Velocity Impact 2.7/100 · LOW

Which changes need focused human review? 42 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 24LOW 18

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 42 distinct pattern matches across 8 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 Separators23 hits · 69 pts
SeverityFileLineSnippetContext
MEDIUMhttpserver/koreader.go30// ── KOReader server state ─────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/koreader.go91// ── KOReader HTTP mux ─────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/koreader.go132// ── Helpers ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/koreader.go169// ── Handlers ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go17// ── OPDS configuration ────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go25// ── Atom / OPDS XML types ─────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go95// ── Book model from SQLite ────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go160// ── Cover file detection ──────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go241// ── XML helpers ───────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go261// ── OPDS handlers ─────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go502// ── Entry builder ─────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/opds.go547// ── OPDS router ───────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/main.go25// ── Configuration ────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/main.go96// ── Helpers ───────────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/main.go201// ── Handlers ──────────────────────────────────────────────────────────────────COMMENT
MEDIUMhttpserver/main.go448// ── Router ────────────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/workflows/docker-publish.yml30 # ── Pre-build React app on native runner (eliminates QEMU overhead) ──────COMMENT
MEDIUMsrc/pages/stats/component.tsx96 // ── 1. Books read (has a recordLocation) ──────────────────────────────COMMENT
MEDIUMsrc/pages/stats/component.tsx111 // ── 2. Total reading time from readingStats ────────────────────────────COMMENT
MEDIUMsrc/pages/stats/component.tsx122 // ── 3. Longest streak (consecutive reading days up to today) ──────────COMMENT
MEDIUMsrc/pages/stats/component.tsx141 // ── 4. Daily average ──────────────────────────────────────────────────COMMENT
MEDIUMsrc/pages/stats/component.tsx148 // ── 5. Last 30 days data ──────────────────────────────────────────────COMMENT
MEDIUMsrc/pages/stats/component.tsx160 // ── 6. Heatmap: last 52 weeks ─────────────────────────────────────────COMMENT
Over-Commented Block9 hits · 9 pts
SeverityFileLineSnippetContext
LOWdocker-compose.yml21# volumes:COMMENT
LOWpublic/lib/sqljs-wasm/sql-wasm.js21 // If we're here, we've never called this function beforeCOMMENT
LOWpublic/lib/7z-wasm/7zz.umd.js961/**COMMENT
LOWpublic/lib/7z-wasm/7zz.umd.js1101 if (codeUnit == 0) break;COMMENT
LOWpublic/lib/7z-wasm/7zz.umd.js5261 // MEMORY_GROWTH_GEOMETRIC_STEP factor (default +20%),COMMENT
LOWpublic/lib/7z-wasm/7zz.umd.js6181 } elseCOMMENT
LOWhttpserver/koreader.go1package mainCOMMENT
LOWsrc/constants/settingList.tsx221 // key: "apiKey",COMMENT
LOWsrc/utils/storage/databaseService.ts141 let records = await this.getAllRecords(dbName);COMMENT
Fake / Example Data4 hits · 4 pts
SeverityFileLineSnippetContext
LOWpublic/lib/highlight-js/highlight.min.js316}),ae=["a","abbr","address","article","aside","audio","b","blockquote","body","button","canvas","caption","cite","code",CODE
LOWpublic/lib/highlight-js/languages/css.min.js3;const e=["a","abbr","address","article","aside","audio","b","blockquote","body","button","canvas","caption","cite","codCODE
LOWpublic/lib/highlight-js/languages/scss.min.js3;const e=["a","abbr","address","article","aside","audio","b","blockquote","body","button","canvas","caption","cite","codCODE
LOWpublic/lib/highlight-js/languages/less.min.js3;const e=["a","abbr","address","article","aside","audio","b","blockquote","body","button","canvas","caption","cite","codCODE
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMsrc/upload.sh31# Create a directory with the name of the tagCOMMENT
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWpublic/lib/7z-wasm/7zz.umd.js1308function updateGlobalBufferAndViews(buf) {CODE
LOWpublic/lib/7z-wasm/7zz.umd.js1738 function receiveInstantiationResult(result) {CODE
Verbosity Indicators1 hit · 2 pts
SeverityFileLineSnippetContext
LOWpublic/lib/7z-wasm/7zz.umd.js17// We need to check if Module already exists (e.g. case 3 above).COMMENT
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWpublic/lib/onnxruntime-web/ort.min.js536 // TODO: implement vectorized powCOMMENT
Overly Generic Function Names1 hit · 1 pts
SeverityFileLineSnippetContext
LOWpublic/lib/7z-wasm/7zz.umd.js4633 function processData(byteArray) {CODE