AI Slop Code Risk Monitor

imgproxy/imgproxy

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

Fast and secure standalone server for resizing, processing, and converting images on the fly

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for imgproxy/imgproxy, a Go project with 11,165 GitHub stars. SynthScan examined 50,642 lines of code across 408 source files, recording 18 pattern matches distributed across 2 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-26

Last Push

11.2K

Stars

Language

50.6K

Lines of Code

408

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

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

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

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 18 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 Block16 hits · 16 pts

Severity	File	Line	Snippet	Context
LOW	logger/handler.go	21	// FormatStructured is a key=value structured format	COMMENT
LOW	logger/handler.go	41	// - groups: a slice of slog.Attr representing the attribute groups added	COMMENT
LOW	asyncbuffer/buffer.go	1	// Package asyncbuffer provides an asynchronous buffer that reads data from an	COMMENT
LOW	processing/crop.go	41	// After rotation and flipping, we'll get the same result	COMMENT
LOW	errctx/error.go	21	// StackTrace returns the stack trace associated with the error.	COMMENT
LOW	errctx/wrapped_error.go	21	ErrorContext: newErrorContext(stackSkip+1, opts...),	COMMENT
LOW	vips/bmp.h	1	/*	COMMENT
LOW	vips/icoload.c	1	// ICO loader	COMMENT
LOW	fetcher/transport/url.go	1	package transport	COMMENT
LOW	privatenet/privatenet.go	1	// Package privatenet classifies IP addresses as private, extending the stdlib	COMMENT
LOW	privatenet/privatenet.go	61	func IsLoopback(ip net.IP) bool {	COMMENT
LOW	examples/encrypted_source_url.rb	21	# We don't sign the URL in this example but it is highly recommended to sign	COMMENT
LOW	testutil/equal_but_not_same.go	101	case string:	COMMENT
LOW	testutil/equal_but_not_same.go	121	// .......----------------===--+ .+#%#++++#= .. =========+=====+++=++=++++++	COMMENT
LOW	testutil/equal_but_not_same.go	141	// ++++++ .%%%#+#### ==##%%%@%%#=%@@@%%###+#%%+=--==-===--------....-#=. +####	COMMENT
LOW	testutil/equal_but_not_same.go	161	// +#+++#+#####++++= .=++##%#%%%%%%%@@@@@@@@@@@@@@@%####%%%%@%%@%%%%%%%%%@@%@%%%%%#	COMMENT

Slop Phrases2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	testutil/lasy_suite.go	11	// so if you also use this function in your test suite, don't forget to call	COMMENT
LOW	testutil/lasy_suite.go	26	// If you also use this function in your test suite, don't forget to call	COMMENT