AI Slop Code Risk Monitor

prisma/prisma-examples

Name: prisma/prisma-examples — 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).

🚀 Ready-to-run Prisma example projects

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for prisma/prisma-examples, a TypeScript project with 6,650 GitHub stars. SynthScan examined 92,361 lines of code across 1073 source files, recording 26 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.3 (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.3

Adjusted Signal

0.3

Raw Pattern Score

100%

Time Factor

2026-11-01

Last Push

6.7K

Stars

TypeScript

Language

92.4K

Lines of Code

1.1K

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

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

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 1.4/100 · LOW

Which changes need focused human review? 26 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 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 26 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 Block21 hits · 21 pts

Severity	File	Line	Snippet	Context
LOW	accelerate/solidstart-starter/src/entry-client.tsx	1	// @refresh reload	COMMENT
LOW	accelerate/astro-starter/src/env.d.ts	1	/// <reference types="astro/client" />	COMMENT
LOW	accelerate/svelte-starter/tsconfig.json	1	{	COMMENT
LOW	…te/room-booking-prisma-template/src/server/bookings.ts	1	import { isPlacementAllowed } from "resource-scheduler/headless";	COMMENT
LOW	orm/elysia/tsconfig.json	1	{	COMMENT
LOW	orm/elysia/tsconfig.json	21	// "jsxImportSource": "", /* Specify module specifier used to import the JSX factory func	COMMENT
LOW	orm/elysia/tsconfig.json	41	/* JavaScript Support */	COMMENT
LOW	orm/elysia/tsconfig.json	61	// "inlineSources": true, /* Include source code in the sourcemaps inside the emitted Jav	COMMENT
LOW	orm/elysia/tsconfig.json	81	// "strictNullChecks": true, /* When type checking, take into account 'null' and 'undefined'	COMMENT
LOW	orm/nextjs-graphql/next-env.d.ts	1	/// <reference types="next" />	COMMENT
LOW	orm/cloudflare-workers/worker-configuration.d.ts	8341	} : T;	COMMENT
LOW	orm/cloudflare-workers/worker-configuration.d.ts	8361	// For properties, rewrite types to be `Result`s.	COMMENT
LOW	orm/cloudflare-workers/worker-configuration.d.ts	8381	interface Env {	COMMENT
LOW	…latforms/edge/cloudflare-workers/with-d1/tsconfig.json	21	// "jsxImportSource": "", /* Specify module specifier used to import the JSX factory functi	COMMENT
LOW	…latforms/edge/cloudflare-workers/with-d1/tsconfig.json	41	/* JavaScript Support */	COMMENT
LOW	…latforms/edge/cloudflare-workers/with-d1/tsconfig.json	61	// "inlineSources": true, /* Include source code in the sourcemaps inside the emitted JavaS	COMMENT
LOW	…latforms/edge/cloudflare-workers/with-d1/tsconfig.json	81	// "strictNullChecks": true, /* When type checking, take into account `null` and `undefined`.	COMMENT
LOW	…extjs-starter-webpack-turborepo/apps/web/next-env.d.ts	1	/// <reference types="next" />	COMMENT
LOW	…r-starter-cloudflare-workerd/worker-configuration.d.ts	6661	// The unique identifier (JWT ID) used by the client to authenticate, if token	COMMENT
LOW	…r-starter-cloudflare-workerd/worker-configuration.d.ts	6721	export type EntrypointBranded = WorkerEntrypointBranded \| DurableObjectBranded \| WorkflowEntrypointBranded;	COMMENT
LOW	…r-starter-cloudflare-workerd/worker-configuration.d.ts	6761	} ? {	COMMENT

Fake / Example Data3 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	orm/betterauth-nextjs/src/app/sign-up/page.tsx	63	placeholder="John Doe"	CODE
LOW	orm/cloudflare-workers/README.md	73	-d '{"email":"john@example.com","name":"John Doe"}'	CODE
LOW	deployment-platforms/railway/src/index.ts	75	name: 'Jane Doe',	CODE

Overly Generic Function Names2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	accelerate/remix-starter/app/entry.server.tsx	26	export default function handleRequest(	CODE
LOW	…router-starter-cloudflare-workerd/app/entry.server.tsx	6	export default async function handleRequest(	CODE