AI Slop Code Risk Monitor

redis/ioredis

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

🚀 A robust, performance-focused, and full-featured Redis client for Node.js.

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for redis/ioredis, a TypeScript project with 15,351 GitHub stars. SynthScan examined 91,822 lines of code across 526 source files, recording 17 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.3 (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.3
Adjusted Signal
0.3
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
15.4K
Stars
TypeScript
Language
91.8K
Lines of Code
526
Files
17
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.8/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

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

Agent Over-Engineering Ratio 0.7/100 · LOW

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

PR Review Velocity Impact 1.5/100 · LOW

Which changes need focused human review? 17 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 2MEDIUM 0LOW 15

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

Hyper-Verbose Identifiers13 hits · 13 pts
SeverityFileLineSnippetContext
LOWtest/functional/socketTimeout.ts90 function assertNoTimeoutAfterConnection(redisInstance: Redis, done: Done) {CODE
LOWlib/autoPipelining.ts98export function getFirstValueInFlattenedArray(CODE
LOWlib/autoPipelining.ts146export function executeWithAutoPipelining(CODE
LOWlib/DataHandler.ts83export default class DataHandler {CODE
LOWlib/DataHandler.ts506function leaveSubscriberModeIfDone(CODE
LOWlib/cluster/util.ts105export function getUniqueHostnamesFromOptions(nodes: RedisOptions[]): string[] {CODE
LOWlib/redis/event_handler.ts307function isProtocolNegotiationError(err: Error): boolean {CODE
LOWlib/redis/event_handler.ts350function abortTransactionFragments(commandQueue: Deque<CommandItem>) {CODE
LOWlib/utils/Commander.ts170function generateScriptingFunction(CODE
LOWlib/maintNotifications/parser.ts15export function parseMaintenanceNotification(CODE
LOWlib/maintNotifications/parser.ts107function isMaintenanceNotificationType(CODE
LOWlib/maintNotifications/index.ts83export function getMaintNotificationsHandshakeCommand(CODE
LOWlib/himport/HimportCoordinator.ts568export function interceptHimportControlCommand(CODE
Cross-Language Confusion (JS/TS)2 hits · 10 pts
SeverityFileLineSnippetContext
HIGHtest/unit/index.ts9 print(new Error("err"));CODE
HIGHtest/unit/index.ts10 print(null, "success");CODE
Over-Commented Block2 hits · 2 pts
SeverityFileLineSnippetContext
LOW…s/runtime-behavior-probe/templates/typescript_probe.ts301 const caseId = process.env.PROBE_CASE_ID ?? 'case-0001';COMMENT
LOWlib/SubscriptionSet.ts1import { CommandNameFlags } from "./Command";COMMENT