Home / deepstreamIO / deepstream.io
AI Slop Code Risk Monitor

deepstreamIO/deepstream.io

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

deepstream.io server

1.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for deepstreamIO/deepstream.io, a TypeScript project with 7,181 GitHub stars. SynthScan examined 41,742 lines of code across 244 source files, recording 57 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 1.2 (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.

1.2
Adjusted Signal
1.2
Raw Pattern Score
100%
Time Factor
2026-10-12
Last Push
7.2K
Stars
TypeScript
Language
41.7K
Lines of Code
244
Files
57
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 5.9/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 0.4/100 · LOW

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

PR Review Velocity Impact 6.6/100 · LOW

Which changes need focused human review? 57 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 57

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

Over-Commented Block53 hits · 46 pts
SeverityFileLineSnippetContext
LOWtest-e2e/steps/server/step-definition-server.ts61// AfterAll((callback) => {COMMENT
LOWconf/config.yml1# GeneralCOMMENT
LOWconf/config.yml41 responseTimeout: 10000COMMENT
LOWconf/config.yml81 # url path for http health-checks, GET requests to this path will return 200 if deepstream is aliveCOMMENT
LOWconf/config.yml101 # # url path for http health-checks, GET requests to this path will return 200 if deepstream is aliveCOMMENT
LOWconf/config.yml141 # amount of time a connection can remain open while not being logged inCOMMENT
LOWconf/config.yml161 # # should the server log invalid auth data, defaults to falseCOMMENT
LOWconf/config.yml181COMMENT
LOWconf/config.yml201 # should the server log invalid auth data, defaults to falseCOMMENT
LOWconf/config.yml221COMMENT
LOWconf/config.yml241 # filename: 'logs.json'COMMENT
LOWconf/config.yml261# AuthenticationCOMMENT
LOWconf/config.yml281 # - type: fileCOMMENT
LOWconf/config.yml301 # # promote the following items from the login auth data into headersCOMMENT
LOWconf/config.yml321 cacheEvacuationInterval: 60000COMMENT
LOWconf/config.yml341# clusterNode:COMMENT
LOWconf/config.yml361# accessKeyId: ${AWS_ACCESS_KEY}COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts1// import * as C from '../../src/constants'COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts21//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts41//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts61// depInit.on('ready', () => {COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts81// expect(uwsMock.pingMessage).to.equal({COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts101// .expects('destroy')COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts121// originalTopic: 5,COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts141//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts161// action: C.EVENT_ACTION.EMIT,COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts181// .once()COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts201// .once()COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts221//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts241// expect(socketWrapper.user).to.equal('test-user')COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts261// authenticationHandlerMock.nextUserValidationResult = trueCOMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts281// client.socketWrapper.close()COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts301// uwsMock.messageHandler([{ topic: C.TOPIC.AUTH, action: C.RPC_ACTION.REQUEST, data: '{"user":"test-user"}' }], cliCOMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts321// client.socketWrapperMockCOMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts341// .expects('destroy')COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts361// client.socketWrapper.close()COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts381// client.socketWrapperMockCOMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts401// })COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts421//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts441// }COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts461// afterEach(done => {COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts481// it('creates a https connection when sslKey and sslCert are provided', done => {COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts501//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts521// }COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts541// } catch (e) {COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts561//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts581// })COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts601// describe('permission passes additional user meta data', () => {COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts621// it('sends an authentication message', () => {COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts641//COMMENT
LOW…c/connection-endpoint/base/connection-endpoint.spec.ts661// expect(connectionEndpoint.onMessages.calls.mostRecent().args[0].authData).to.deep.equal({ role: 'admin' })COMMENT
LOWsrc/service/template/initd.ts1export default (d: any) =>COMMENT
LOWsrc/handlers/rpc/rpc-handler.spec.ts421 // config.RPCRequestorNameTerm = nullCOMMENT
Hyper-Verbose Identifiers3 hits · 3 pts
SeverityFileLineSnippetContext
LOWsrc/config/js-yaml-loader.ts207function replaceEnvironmentVariables (fileContent: string): string {CODE
LOWsrc/config/config-initialiser.ts257function handleConnectionEndpoints (config: DeepstreamConfig, services: any): DeepstreamConnectionEndpoint[] {CODE
LOWsrc/config/config-initialiser.ts418function handlePermissionStrategies (config: DeepstreamConfig, services: DeepstreamServices): DeepstreamPermission {CODE
TODO Padding1 hit · 2 pts
SeverityFileLineSnippetContext
LOWsrc/connection-endpoint/http/connection-endpoint.ts99 // TODO: implement a GET endpoint that reads the current state of a recordCOMMENT