AI Slop Code Risk Monitor

h3js/h3

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

⚡️ Minimal H(TTP) framework built for high performance and portability

0.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for h3js/h3, a TypeScript project with 5,512 GitHub stars. SynthScan examined 60,909 lines of code across 244 source files, recording 35 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 0.6 (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.6
Adjusted Signal
0.6
Raw Pattern Score
100%
Time Factor
2026-10-22
Last Push
5.5K
Stars
TypeScript
Language
60.9K
Lines of Code
244
Files
35
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 2.8/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 35 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.8/100 · LOW

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

PR Review Velocity Impact 2.8/100 · LOW

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

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 35 distinct pattern matches across 2 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 Block25 hits · 25 pts
SeverityFileLineSnippetContext
LOWtest/static.test.ts301 // `%255c` survives `resolveDotSegments` (a single `%5c` is decoded to `\`COMMENT
LOWtest/dist.test.ts1import { describe, it, expect, beforeAll } from "vitest";COMMENT
LOWtest/bench/path.ts1import { bench, summary, compact, do_not_optimize, run } from "mitata";COMMENT
LOWtest/rules/treeshake.test.ts1import { dirname, join } from "node:path";COMMENT
LOWtest/rules/treeshake.test.ts21// - The `ufo` absence assertions became absence assertions onCOMMENT
LOWtest/rules/merge.test.ts361 expect(match("GET", "/policy-strip/off/x").routeRules.cors).toBeUndefined();COMMENT
LOWtest/rules/merge.test.ts421 // reading — no co-matching protector deletes it first. `/app/admin/**`COMMENT
LOWtest/rules/merge.test.ts481 // proving the matrix above passes because the paths stay admin — not becauseCOMMENT
LOWtest/rules/types.test-d.ts141declare const matched: MatchedRouteRules;COMMENT
LOWtest/rules/types.test-d.ts161// built-ins are composed in by `ResolvedRouteRules` for the keys nobody claimed.COMMENT
LOWtest/rules/encoding.test.ts41 },COMMENT
LOWtest/rules/match.test.ts241// ---------------------------------------------------------------------------COMMENT
LOWtest/rules/_augment.ts1// The runtime tests (and the bench fixture) exercise data-only / custom rulesCOMMENT
LOWsrc/event.ts101 // built by `mockEvent()` or a standalone `handler.fetch()`, which neverCOMMENT
LOWsrc/utils/path.ts61 */COMMENT
LOWsrc/utils/static.ts121 throw new HTTPError({ status: 405 });COMMENT
LOWsrc/utils/static.ts141 // under their canonical spelling — the one the router sees — only.COMMENT
LOWsrc/utils/proxy.ts341 )COMMENT
LOWsrc/utils/proxy.ts361 // where no signal aborted — is never mistaken for an abort.COMMENT
LOWsrc/utils/internal/path.ts101 const end = path.search(/[#?]/);COMMENT
LOWsrc/utils/internal/path.ts121// this whole pass exists to withhold.COMMENT
LOWsrc/utils/internal/path.ts181// (the WHATWG path percent-encode set) and that carry no meaning in a rou3COMMENT
LOWsrc/rules/handlers/_utils.ts121 // A derived base satisfies the literal test by construction; `isPathInScope`COMMENT
LOWsrc/rules/handlers/headers.ts1import type { HTTPError } from "../../error.ts";COMMENT
LOWsrc/rules/handlers/_splat.ts21const QUERY_UNSAFE_RE = /[#&+;=?]/g;COMMENT
Hyper-Verbose Identifiers10 hits · 10 pts
SeverityFileLineSnippetContext
LOWsrc/utils/json-rpc.ts289export function defineJsonRpcWebSocketHandler(opts: {CODE
LOWsrc/utils/json-rpc.ts509function mapHttpStatusToJsonRpcError(status: number): number {CODE
LOWsrc/utils/cors.ts117export function appendCorsPreflightHeaders(event: H3Event, options: CorsOptions): void {CODE
LOWsrc/utils/internal/path.ts328export function decodePreservingSeparators(CODE
LOWsrc/utils/internal/event-stream.ts43export function formatEventStreamMessages(messages: EventStreamMessage[]): string {CODE
LOWsrc/rules/cache.ts208function withPreservedCacheControl(CODE
LOWsrc/rules/internal/scope.ts202function isEveryCanonicalReadingInScope(pathname: string, base: string): boolean {CODE
LOWsrc/rules/compiler/codegen.ts8export function serializePreMergedRouteRules(CODE
LOWsrc/rules/compiler/codegen.ts29export function serializeRouteRuleEntries(CODE
LOWsrc/rules/compiler/codegen.ts144function assertSerializableOptions(value: unknown, entry: RouteRuleEntry, path: string): void {CODE