AI Slop Code Risk Monitor

nitrojs/nitro

Name: nitrojs/nitro — TypeScript Code Quality & Security Review | AI Slop Code Risk Monitor
Creator: AI Slop Code Risk Monitor

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

Next Generation Server Toolkit. Create web servers with everything you need and deploy them wherever you prefer.

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for nitrojs/nitro, a TypeScript project with 11,338 GitHub stars. SynthScan examined 93,222 lines of code across 1171 source files, recording 27 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.4 (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.4

Adjusted Signal

0.4

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

11.3K

Stars

TypeScript

Language

93.2K

Lines of Code

1.2K

Files

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.4/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

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

Agent Over-Engineering Ratio 1.0/100 · LOW

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

PR Review Velocity Impact 1.9/100 · LOW

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

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

Hyper-Verbose Identifiers18 hits · 18 pts

Severity	File	Line	Snippet	Context
LOW	test/presets/vercel.test.ts	1126	async function testVercelWebSocketUpgrade(	CODE
LOW	src/config/resolvers/export-conditions.ts	3	export async function resolveExportConditionsOptions(options: NitroOptions) {	CODE
LOW	src/config/resolvers/runtime-config.ts	5	export async function resolveRuntimeConfigOptions(options: NitroOptions) {	CODE
LOW	src/config/resolvers/runtime-config.ts	39	function checkSerializableRuntimeConfig(obj: any, path: string[] = []) {	CODE
LOW	src/config/resolvers/tracing.ts	5	export async function resolveTracingChannelOptions(options: NitroOptions) {	CODE
LOW	src/config/resolvers/compatibility.ts	4	export async function resolveCompatibilityOptions(options: NitroOptions) {	CODE
LOW	src/runtime/internal/app.ts	107	export function createRouteRulesMiddleware(): Middleware {	CODE
LOW	src/runtime/internal/app.ts	126	export function createCacheRuleMiddleware(): Middleware {	CODE
LOW	src/runtime/internal/app.ts	166	export function createMethodNotAllowedMatcher(	CODE
LOW	src/utils/database.ts	24	export async function resolveDatabaseConnections(	CODE
LOW	src/dev/_devtools-json.ts	16	export function createDevToolsJSONHandler(nitro: Nitro) {	CODE
LOW	src/dev/_proxy.ts	84	export function createWorkerWebSocketProxy(	CODE
LOW	src/presets/vercel/utils.ts	706	async function createFunctionDirWithCustomConfig(	CODE
LOW	src/presets/vercel/immutable.ts	38	export function setupImmutableStaticFiles(nitro: Nitro) {	CODE
LOW	src/presets/vercel/immutable.ts	69	export async function generateImmutableManifest(nitro: Nitro) {	CODE
LOW	src/presets/azure/_functions.ts	77	async function getInstalledFunctionsVersion(rootDir: string): Promise<number \| undefined> {	CODE
LOW	src/presets/azure/runtime/_utils.ts	4	export function getAzureParsedCookiesFromHeaders(headers: Headers): Cookie[] {	CODE
LOW	src/presets/netlify/utils.ts	102	export function generateNetlifyEdgeFunction(nitro: Nitro) {	CODE

Hallucination Indicators1 hit · 10 pts

Severity	File	Line	Snippet	Context
CRITICAL	src/presets/azure/utils.ts	94	for (const customRoute of nitro.options.azure.config.routes.reverse()) {	CODE

Over-Commented Block7 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW	docs/.docs/utils/definePageMeta.ts	1	// `definePageMeta` stand-in for the undocs theme layer (there are no auto-imports).	COMMENT
LOW	scripts/release.ts	101	const localHead = run("git rev-parse HEAD", { silent: true }).trim();	COMMENT
LOW	scripts/release.ts	121	// ) as CIRun[];	COMMENT
LOW	scripts/release.ts	141	// console.log(` ${jobIcon} ${job.name}`);	COMMENT
LOW	src/dev/server.ts	41	}	COMMENT
LOW	src/presets/vercel/immutable.ts	1	import { glob } from "tinyglobby";	COMMENT
LOW	src/presets/cloudflare/output-plugins.ts	1	import type { Plugin } from "rollup";	COMMENT

Overly Generic Function Names1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	test/unit/telemetry-logger.test.ts	38	async function handleRequest(path: string, ops: Array<Parameters<typeof traced>>): Promise<void> {	CODE