AI Slop Code Risk Monitor

go-chi/chi

Name: go-chi/chi — Go 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).

lightweight, idiomatic and composable router for building Go HTTP services

2.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for go-chi/chi, a Go project with 23,034 GitHub stars. SynthScan examined 14,730 lines of code across 99 source files, recording 38 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 2.8 (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.

2.8

Adjusted Signal

2.8

Raw Pattern Score

100%

Time Factor

2026-10-18

Last Push

23.0K

Stars

Language

14.7K

Lines of Code

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

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

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

PR Review Velocity Impact 12.7/100 · LOW

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

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 38 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 Block35 hits · 35 pts

Severity	File	Line	Snippet	Context
LOW	mux.go	361		COMMENT
LOW	context_test.go	1	package chi	COMMENT
LOW	chi.go	1	// Package chi is a small, idiomatic and composable router for building HTTP services.	COMMENT
LOW	chi.go	21	// r.Get("/", func(w http.ResponseWriter, r *http.Request) {	COMMENT
LOW	chi.go	41	// expression match, for example {number:\\d+}. The regular expression	COMMENT
LOW	context.go	41	// request context to track route patterns, URL parameters and	COMMENT
LOW	mux_test.go	1121	// rr1 = r.(*Mux)	COMMENT
LOW	mux_test.go	1321	// XX string	COMMENT
LOW	middleware/client_ip.go	21	//	COMMENT
LOW	middleware/client_ip.go	41	// stripped before storage.	COMMENT
LOW	middleware/client_ip.go	81	// of the given trusted CIDR prefixes. The first IP that is not trusted is	COMMENT
LOW	middleware/client_ip.go	101	// ))	COMMENT
LOW	middleware/client_ip.go	161	// numTrustedProxies = total proxy hops between the client and this server.	COMMENT
LOW	middleware/client_ip.go	201	}	COMMENT
LOW	middleware/client_ip.go	241	// the ClientIPFrom* middlewares. The returned Addr is the zero value if not	COMMENT
LOW	middleware/route_headers.go	1	package middleware	COMMENT
LOW	middleware/route_headers.go	21	// rSubdomain.Get("/", h2)	COMMENT
LOW	middleware/client_ip_test.go	601	}	COMMENT
LOW	middleware/logger.go	21	)	COMMENT
LOW	middleware/sunset.go	1	package middleware	COMMENT
LOW	middleware/timeout.go	1	package middleware	COMMENT
LOW	middleware/timeout.go	21	//	COMMENT
LOW	middleware/wrap_writer.go	41	}	COMMENT
LOW	middleware/deprecation.go	1	package middleware	COMMENT
LOW	middleware/client_ip_example_test.go	21	//	COMMENT
LOW	middleware/client_ip_example_test.go	41	r := chi.NewRouter()	COMMENT
LOW	middleware/compress.go	101	allowedTypes: allowedTypes,	COMMENT
LOW	middleware/compress.go	121	// both ways, first looking for zlib headers.	COMMENT
LOW	middleware/compress.go	141	return c	COMMENT
LOW	middleware/url_format.go	21	// Routers should not include a url parameter for the suffix when using this middleware.	COMMENT
LOW	middleware/request_id.go	21	const RequestIDKey ctxKeyRequestID = 0	COMMENT
LOW	_examples/fileserver/main.go	1	// This example demonstrates how to serve static files from your filesystem.	COMMENT
LOW	_examples/rest/main.go	1	// This example demonstrates a HTTP REST web service with some fixture data.	COMMENT
LOW	_examples/rest/main.go	21	//	COMMENT
LOW	_examples/rest/main.go	381	list = append(list, NewArticleResponse(article))	COMMENT

Structural Annotation Overuse2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	README.md	494	// Step 1: the route is deprecated.	COMMENT
LOW	README.md	497	// Step 2: the removal date is known.	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	middleware/client_ip.go	157	// cannot off-by-one and is robust to architecture changes. Most CDNs	COMMENT