AI Slop Code Risk Monitor

quay/clair

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

Vulnerability Static Analysis for Containers

0.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for quay/clair, a Go project with 11,086 GitHub stars. SynthScan examined 42,624 lines of code across 303 source files, recording 35 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.9 (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.9

Adjusted Signal

0.9

Raw Pattern Score

100%

Time Factor

2026-10-30

Last Push

11.1K

Stars

Language

42.6K

Lines of Code

303

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

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

PR Review Velocity Impact 4.5/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 2LOW 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 35 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 Block32 hits · 32 pts

Severity	File	Line	Snippet	Context
LOW	cmd/config.go	21	// If a directory suffixed with ".d" exists (e.g. a file "config.json" and a directory "config.json.d"),	COMMENT
LOW	Documentation/reference/config.md	141	a starting point for configuration will result in some options not having their	COMMENT
LOW	notifier/store.go	21	Notifications []Notification	COMMENT
LOW	notifier/store.go	41	// paging has been exhausted.	COMMENT
LOW	notifier/store.go	61	// CollectNotifications garbage collects all notifications.	COMMENT
LOW	notifier/mockstore.go	21	SetDeliveredFailed_ func(ctx context.Context, id uuid.UUID) error	COMMENT
LOW	notifier/processor.go	21	// these notifications for later retrieval.	COMMENT
LOW	notifier/deliverer.go	21	// DirectDeliverer(s) expect this method to be called prior to their Deliverer methods.	COMMENT
LOW	notifier/amqp/doc.go	1	// Package amqp implements a [Deliverer] over the AMQP protocol.	COMMENT
LOW	notifier/postgres/e2e_test.go	41	//	COMMENT
LOW	notifier/stomp/doc.go	1	// Package stomp implements a [Deliverer] over the STOMP protocol.	COMMENT
LOW	config/otlp.go	21	Headers map[string]string `yaml:"headers,omitempty" json:"headers,omitempty"`	COMMENT
LOW	config/config.go	1	package config	COMMENT
LOW	config/matcher.go	1	package config	COMMENT
LOW	config/matcher.go	21	IndexerAddr string `yaml:"indexer_addr" json:"indexer_addr"`	COMMENT
LOW	config/matcher.go	41	// database, so see	COMMENT
LOW	config/notifier.go	21	// Configures the notifier for STOMP delivery.	COMMENT
LOW	config/notifier.go	41	//	COMMENT
LOW	config/notifier.go	201	// Exchange are the required fields necessary to check	COMMENT
LOW	config/notifier.go	241	// The first successful connection will be used by the amqp deliverer.	COMMENT
LOW	config/notifier.go	321	// optional tls portion of config	COMMENT
LOW	config/lint_test.go	21	var c Config	COMMENT
LOW	config/indexer.go	1	package config	COMMENT
LOW	config/indexer.go	21	// A positive values representing quantity.	COMMENT
LOW	config/doc.go	1	// Package config is the configuration package for Clair's binaries. See the	COMMENT
LOW	config/doc.go	21	// "empty" aren't distinguished. This would be much easier if code didn't	COMMENT
LOW	config/updaters.go	1	package config	COMMENT
LOW	config/updaters.go	21	// The following sets are supported by default:	COMMENT
LOW	config/matchers.go	1	package config	COMMENT
LOW	httptransport/api/openapi.zsh	1	#!/usr/bin/zsh	COMMENT
LOW	contrib/cmd/quaybackstop/main.go	1	//go:build go1.23	COMMENT
LOW	local-dev/clair/config.yaml	41	# exchange:	COMMENT

AI Slop Vocabulary2 hits · 6 pts

Severity	File	Line	Snippet	Context
MEDIUM	config/notifier.go	257	// utilize the pagination API to retrieve.	COMMENT
MEDIUM	config/notifier.go	346	// utilize the pagination API to retrieve.	COMMENT

Structural Annotation Overuse1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	…hift/grafana/dashboards/dashboard-clair.configmap.yaml	1	# WARNING: This is generated from local-dev/grafana/data/dashboards/clair.json	COMMENT