AI Slop Code Risk Monitor

swagger-api/swagger-ui

Name: swagger-api/swagger-ui — JavaScript 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).

Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for swagger-api/swagger-ui, a JavaScript project with 29,067 GitHub stars. SynthScan examined 142,264 lines of code across 1063 source files, recording 37 pattern matches distributed across 6 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-10-30

Last Push

29.1K

Stars

JavaScript

Language

142.3K

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

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.4/100 · LOW

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

PR Review Velocity Impact 1.6/100 · LOW

Which changes need focused human review? 37 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 4LOW 33

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 37 distinct pattern matches across 6 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 Data9 hits · 11 pts

Severity	File	Line	Snippet	Context
LOW	…st/unit/core/plugins/json-schema-2020-12-samples/fn.js	21	"user@example.com"	CODE
LOW	…st/unit/core/plugins/json-schema-2020-12-samples/fn.js	233	).toStrictEqual('{"name": "John Doe"}')	CODE
LOW⚡	…ight/static/documents/bugs/7996-tags-externalDocs.yaml	7	description: "Foo: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore	CODE
LOW⚡	…ight/static/documents/bugs/7996-tags-externalDocs.yaml	7	description: "Foo: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore	CODE
LOW⚡	…ight/static/documents/bugs/7996-tags-externalDocs.yaml	13	description: "Bar: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore	CODE
LOW⚡	…ight/static/documents/bugs/7996-tags-externalDocs.yaml	13	description: "Bar: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore	CODE
LOW	…ins/json-schema-2020-12-samples/fn/generators/email.js	4	const emailGenerator = () => "user@example.com"	CODE
LOW	…20-12-samples/fn/generators/media-types/application.js	9	"application/ld+json": () => '{"name": "John Doe"}',	CODE
LOW	src/core/plugins/json-schema-5-samples/fn/index.js	30	"string_email": () => "user@example.com",	CODE

Hyper-Verbose Identifiers11 hits · 11 pts

Severity	File	Line	Snippet	Context
LOW	test/e2e-playwright/features/deep-linking.spec.ts	214	function operationDeeplinkTestFactory({	CODE
LOW	test/e2e-playwright/support/multiple-examples.ts	47	export function ParameterPrimitiveTestCases({	CODE
LOW	test/e2e-playwright/support/multiple-examples.ts	171	export function RequestBodyPrimitiveTestCases({	CODE
LOW	test/e2e-playwright/support/multiple-examples.ts	480	export function ResponsePrimitiveTestCases({	CODE
LOW	src/core/system.js	17	function createStoreWithMiddleware(rootReducer, initialState, getSystem) {	CODE
LOW	…err/error-transformers/transformers/parameter-oneof.js	30	function createTailoredParameterError(err, jsSpec) {	CODE
LOW	src/core/plugins/oas3/selectors.js	33	function validateRequestBodyIsRequired(selector) {	CODE
LOW	src/core/plugins/oas3/actions.js	67	export function setResponseCodeContentType ({ value, path, method, code }) {	CODE
LOW	src/core/utils/index.js	236	export function extractFileNameFromContentDispositionHeader(value){	CODE
LOW	src/core/utils/index.js	675	export function getAcceptControllingResponse(responses) {	CODE
LOW	src/core/utils/jsonParse.js	11	export function getKnownSyntaxHighlighterLanguage(val) {	CODE

Structural Annotation Overuse6 hits · 9 pts

Severity	File	Line	Snippet	Context
LOW	.claude/skills/add-json-schema-support/SKILL.md	41	## Step 0: Where to Start	COMMENT
LOW	.claude/skills/add-json-schema-support/SKILL.md	51	## Step 1: Decisions	COMMENT
LOW	.claude/skills/add-json-schema-support/SKILL.md	65	## Step 2: Research the Draft	COMMENT
LOW	.claude/skills/add-json-schema-support/SKILL.md	84	## Step 3: Keyword Map and PR Plan	COMMENT
LOW	.claude/skills/add-json-schema-support/SKILL.md	102	## Step 4: PR 1, Detection and Document	COMMENT
LOW	.claude/skills/add-json-schema-support/SKILL.md	138	## Step 5: Keyword PRs	COMMENT

Over-Commented Block7 hits · 7 pts

Severity	File	Line	Snippet	Context
LOW	test/unit/core/plugins/spec/selectors.js	341	}	COMMENT
LOW	.github/workflows/codeql.yml	1	# For most projects, this workflow file will not need changing; you simply need	COMMENT
LOW	src/core/system.js	501	const store = createStoreWithMiddleware(rootReducer, initialState, getSystem)	COMMENT
LOW	src/core/plugins/json-schema-5-samples/fn/index.js	221	type = "object"	COMMENT
LOW	src/core/components/initialized-input.jsx	1	// This component provides an interface that feels like an uncontrolled input	COMMENT
LOW	src/style/_dark-mode.scss	41	#6a6a6a,	COMMENT
LOW	src/style/_dark-mode.scss	61	patch: (	COMMENT

Slop Phrases3 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	test/unit/core/plugins/spec/assets/petstore.json	4	"description": "This is a sample server Petstore server. You can find out more about Swagger at [http://swagger.io]	CODE
MEDIUM	test/e2e-selenium/static/test-specs/petstore.json	4	"description":"This is a sample server Petstore server. You can find out more about Swagger at [http://swagger.io	CODE
MEDIUM	…e2e-playwright/static/documents/bugs/5043/swagger.yaml	3	description: "This is a sample server Petstore server. You can find out more about Swagger at [http://swagger.io]	CODE

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	flavors/swagger-ui-react/release/run.sh	21	# Create a releasable package manifest	COMMENT