AI Slop Code Risk Monitor

socketio/socket.io

SlopCodeMonitor badge for socketio/socket.io Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Bidirectional and low-latency communication for every platform

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for socketio/socket.io, a TypeScript project with 63,233 GitHub stars. SynthScan examined 104,506 lines of code across 690 source files, recording 34 pattern matches distributed across 7 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-09-29
Last Push
63.2K
Stars
TypeScript
Language
104.5K
Lines of Code
690
Files
34
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.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 1.3/100 · LOW

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

Agent Over-Engineering Ratio 0.2/100 · LOW

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

PR Review Velocity Impact 2.4/100 · LOW

Which changes need focused human review? 34 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 1HIGH 0MEDIUM 4LOW 29

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 34 distinct pattern matches across 7 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.

Fake / Example Data15 hits · 17 pts
SeverityFileLineSnippetContext
LOWexamples/nextjs-pages-router/src/pages/api/hello.js4 res.status(200).json({ name: "John Doe" });CODE
LOW…-application/server/test/todo-management/todo.tests.ts60 title: "lorem ipsum",CODE
LOW…-application/server/test/todo-management/todo.tests.ts72 title: "lorem ipsum",CODE
LOW…-application/server/test/todo-management/todo.tests.ts82 expect(todo.title).to.eql("lorem ipsum");CODE
LOW…-application/server/test/todo-management/todo.tests.ts119 title: "lorem ipsum",CODE
LOW…-application/server/test/todo-management/todo.tests.ts131 expect(res.data.title).to.eql("lorem ipsum");CODE
LOW⚡…-application/server/test/todo-management/todo.tests.ts171 title: "lorem ipsum",CODE
LOW⚡…-application/server/test/todo-management/todo.tests.ts179 title: "dolor sit amet",CODE
LOW⚡…-application/server/test/todo-management/todo.tests.ts188 title: "dolor sit amet",CODE
LOW⚡…-application/server/test/todo-management/todo.tests.ts196 expect(todo.title).to.eql("dolor sit amet");CODE
LOW…-application/server/test/todo-management/todo.tests.ts242 title: "lorem ipsum",CODE
LOW…-application/server/test/todo-management/todo.tests.ts279 title: "lorem ipsum",CODE
LOW…-application/server/test/todo-management/todo.tests.ts285 title: "dolor sit amet",CODE
LOW…-application/server/test/todo-management/todo.tests.ts296 title: "lorem ipsum",CODE
LOW…-application/server/test/todo-management/todo.tests.ts301 title: "dolor sit amet",CODE
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALpackages/socket.io-component-emitter/test/emitter.js155 emitter._callbacks.should.not.have.property('$foo');CODE
Modern AI Meta-Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMexamples/angular-todomvc/README.md17## Code scaffoldingCOMMENT
MEDIUM…amples/basic-crud-application/angular-client/README.md9## Code scaffoldingCOMMENT
Structural Annotation Overuse4 hits · 6 pts
SeverityFileLineSnippetContext
LOWexamples/ReactNativeExample/README.md7## Step 1: Start the Metro ServerCOMMENT
LOWexamples/ReactNativeExample/README.md21## Step 2: Start your ApplicationCOMMENT
LOWexamples/ReactNativeExample/README.md49## Step 3: Start the Socket.IO serverCOMMENT
LOWexamples/ReactNativeExample/README.md59## Step 4: Modifying your AppCOMMENT
Over-Commented Block6 hits · 6 pts
SeverityFileLineSnippetContext
LOWexamples/create-react-app-example/src/serviceWorker.js1// This optional code is used to register a service worker.COMMENT
LOWexamples/create-react-app-example/src/setupTests.js1// jest-dom adds custom jest matchers for asserting on DOM nodes.COMMENT
LOWexamples/typescript-check-public-exports/tsconfig.json1{COMMENT
LOWpackages/socket.io-parser/test/support/env.js1// WARNING this is bad practiceCOMMENT
LOW.github/workflows/ci-engine.io-client.yml61 - name: Run tests with Node.js native WebSocketCOMMENT
LOW.github/workflows/ci-engine.io-parser.yml41COMMENT
AI Slop Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMpackages/engine.io/lib/server.ts779 // try to leverage pre-existing `req._query` (e.g: from connect)COMMENT
MEDIUMpackages/engine.io/lib/transports/polling-jsonp.ts23 // we leverage the qs module so that we get built-in DoS protectionCOMMENT
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOWpackages/socket.io/client-dist/socket.io.js382 function createPacketEncoderStream() {CODE
LOWpackages/socket.io/client-dist/socket.io.js437 function createPacketDecoderStream(maxPayload, binaryType) {CODE
LOWpackages/engine.io-parser/lib/index.ts49export function createPacketEncoderStream(): any {CODE
LOWpackages/engine.io-parser/lib/index.ts113export function createPacketDecoderStream(CODE