AI Slop Code Risk Monitor

nodemailer/nodemailer

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

✉️ Send e-mails with Node.JS – easy as cake!

1.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nodemailer/nodemailer, a TypeScript project with 17,700 GitHub stars. SynthScan examined 61,081 lines of code across 155 source files, recording 53 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 1.1 (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.1
Adjusted Signal
1.1
Raw Pattern Score
100%
Time Factor
2026-10-29
Last Push
17.7K
Stars
TypeScript
Language
61.1K
Lines of Code
155
Files
53
Pattern Hits
2026-10-31
Scan Date
0.01
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.0/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 4.4/100 · LOW

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

Agent Over-Engineering Ratio 0.3/100 · LOW

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

PR Review Velocity Impact 5.0/100 · LOW

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

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 53 distinct pattern matches across 4 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 Data40 hits · 44 pts
SeverityFileLineSnippetContext
LOW⚡test/addressparser/addressparser-test.ts513 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts520 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts527 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts580 let input = 'John Doe';CODE
LOW⚡test/addressparser/addressparser-test.ts583 assert.strictEqual(result[0].name, 'John Doe');CODE
LOW⚡test/addressparser/addressparser-test.ts591 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts728 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts736 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts743 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts788 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts795 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts802 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOW⚡test/addressparser/addressparser-test.ts1605 assert.deepStrictEqual(addressparser('"John Doe" user@example.com'), [{ address: 'user@example.com', name: 'CODE
LOW⚡test/addressparser/addressparser-test.ts1605 assert.deepStrictEqual(addressparser('"John Doe" user@example.com'), [{ address: 'user@example.com', name: 'CODE
LOW⚡test/addressparser/addressparser-test.ts1606 assert.deepStrictEqual(addressparser('"John Doe"'), [{ address: '', name: 'John Doe' }]);CODE
LOW⚡test/addressparser/addressparser-test.ts1607 assert.deepStrictEqual(addressparser('"John Doe" nothing'), [{ address: '', name: 'John Doe nothing' }]);CODE
LOWtest/addressparser/addressparser-test.ts474 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOWtest/addressparser/addressparser-test.ts481 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOWtest/addressparser/addressparser-test.ts698 assert.strictEqual(result[0].address, 'user@example.com');CODE
LOWtest/addressparser/addressparser-test.ts1109 assert.strictEqual(result[0].group[0].address, 'user@example.com');CODE
LOWtest/addressparser/addressparser-test.ts1120 assert.strictEqual(result[0].group[0].address, 'user@example.com');CODE
LOWtest/addressparser/addressparser-test.ts1130 assert.deepStrictEqual(result[0].group, [{ address: 'user@example.com', name: '' }]);CODE
LOWtest/addressparser/addressparser-test.ts1503 assert.deepStrictEqual(addressparser(input), [{ address: 'user@example.com', name: 'Name' }], input);CODE
LOWtest/addressparser/addressparser-test.ts1517 assert.deepStrictEqual(addressparser('<user@example.com(John Doe)>'), [{ address: 'user@example.com', name: CODE
LOWtest/addressparser/addressparser-test.ts1517 assert.deepStrictEqual(addressparser('<user@example.com(John Doe)>'), [{ address: 'user@example.com', name: CODE
LOWtest/addressparser/addressparser-test.ts1593 ['"user"@example.com', 'user@example.com'],CODE
LOWtest/addressparser/addressparser-test.ts1776 ['user@example.com (outer (nested) comment)', [{ address: 'user@example.com', name: 'outer (nested) commCODE
LOWtest/addressparser/addressparser-test.ts1834 ['Name <<user@example.com>>', [{ address: 'user@example.com', name: 'Name>' }]],CODE
LOWtest/mime-node/mime-node-test.ts1588 // whitespace makes 'John Doe' a display name rather than a local username, so itCOMMENT
LOWtest/mime-node/mime-node-test.ts1590 assert.deepStrictEqual(new MimeNode().setEnvelope({ from: 'a@example.com', to: ['John Doe'] }).getEnvelope()CODE
LOWtest/mime-node/mime-node-test.ts2057 const encoded = MimeNode.encodeHeaderValue('To', [{ name, address: 'user@example.com' }, 'other@examCODE
LOWtest/mime-node/mime-node-test.ts2062 assert.strictEqual(parsed[0].address, 'user@example.com', message);CODE
LOWtest/mime-node/mime-node-test.ts2280 mb._convertAddresses([{ address: 'user@example.com' }, { address: 'other@example.com' }]),CODE
LOWtest/xoauth2/xoauth2-tls-test.ts82 user: 'user@example.com',CODE
LOWtest/xoauth2/xoauth2-tls-test.ts103 user: 'user@example.com',CODE
LOWtest/smtp-transport/oauth2-listener-leak-test.ts91 user: 'user@example.com',CODE
LOWtest/smtp-transport/oauth2-provision-test.ts24 if (auth.method !== 'XOAUTH2' || auth.username !== 'user@example.com' || auth.accessToken !== 'provisionCODE
LOWtest/smtp-transport/oauth2-provision-test.ts56 user: 'user@example.com'CODE
LOWtest/smtp-transport/oauth2-provision-test.ts63 assert.strictEqual(user, 'user@example.com');CODE
LOWtest/smtp-transport/oauth2-provision-test.ts102 user: 'user@example.com'CODE
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALtest/ses-transport/ses-transport-test.ts415 assert.ok(messageData.messageData.Content.Raw.Data.toString().includes('h=from:subject:to:cc:mimCODE
Over-Commented Block8 hits · 8 pts
SeverityFileLineSnippetContext
LOWscripts/build.js1// Builds the package.COMMENT
LOWscripts/build.js81COMMENT
LOWsrc/addressparser/index.ts701 // An empty quoted string is dropped by the tokenizer, leaving no text token of itsCOMMENT
LOWsrc/addressparser/index.ts801 // tiers read the collapsed runs, and only a run an address comes out of is replacedCOMMENT
LOWsrc/addressparser/index.ts881 //COMMENT
LOWsrc/mime-node/index.ts241 }COMMENT
LOWsrc/mime-node/index.ts1661 * @internalCOMMENT
LOWsrc/shared/url.ts1// URL parsing wrapper around the WHATWG `URL` class. It only falls back to theCOMMENT
Hyper-Verbose Identifiers4 hits · 4 pts
SeverityFileLineSnippetContext
LOWtest/smtp-transport/oauth2-listener-leak-test.ts35function startDropDuringAuthServer(callback: (server: net.Server, port: number) => void) {CODE
LOWscripts/build.js43function generateWellKnownServices() {CODE
LOWsrc/mime-node/index.ts227function stripWhitespaceInAngleBrackets(value: string): string {CODE
LOWsrc/shared/url.ts55function stripSurroundingWhitespace(input: string): string {CODE