AI Slop Code Risk Monitor

docker/buildx

Name: docker/buildx — open-source 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).

0.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for docker/buildx. SynthScan examined 101,267 lines of code across 436 source files, recording 40 pattern matches distributed across 5 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

—

Last Push

—

Stars

—

Language

101.3K

Lines of Code

436

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

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

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

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 40 distinct pattern matches across 5 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	util/confutil/container.go	61	// The following BuildKit config:	COMMENT
LOW	util/otelutil/span.go	21	// for handle marshaling and unmarshalling.	COMMENT
LOW	util/otelutil/span.go	41	Links []tracesdk.Link	COMMENT
LOW	util/userfunc/public.go	1	package userfunc	COMMENT
LOW	util/userfunc/doc.go	1	// Package userfunc implements a HCL extension that allows user-defined	COMMENT
LOW	driver/kubernetes/context/load.go	181	return clientcmd.NewDefaultClientConfig(*apiConfig, &clientcmd.ConfigOverrides{}), nil	COMMENT
LOW	tests/version.go	21		COMMENT
LOW	bake/hclparser/type_implied.go	1	// MIT License	COMMENT
LOW	bake/hclparser/type_implied.go	21	// SOFTWARE.	COMMENT
LOW	bake/hclparser/gohcl/encode.go	21	// fields tagged as "remain", any fields that decode attributes into either	COMMENT
LOW	bake/hclparser/gohcl/doc.go	1	// Copyright (c) HashiCorp, Inc.	COMMENT
LOW	bake/hclparser/gohcl/doc.go	21	// block indicates that the value is to populated from a block	COMMENT
LOW	bake/hclparser/gohcl/doc.go	41	// "label" fields are considered only in a struct used as the type of a field	COMMENT
LOW	bake/hclparser/gohcl/doc.go	61	// written with the configuration author as the target audience. The second	COMMENT
LOW	bake/hclparser/gohcl/decode.go	321	// DecodeExpression extracts the value of the given expression into the given	COMMENT
LOW	bake/hclparser/gohcl/encode_test.go	61	// service "web" {	COMMENT
LOW	commands/util.go	21	}()	COMMENT
LOW	commands/replay/build.go	421	// - platformFilter empty keeps the only subject when at most one subject	COMMENT
LOW	replay/snapshot_format.go	21		COMMENT
LOW	replay/snapshot_format.go	61	// image-manifest document plus its serialized bytes and descriptor) from the	COMMENT
LOW	replay/snapshot_format.go	101	// into the snapshot content store by the caller.	COMMENT
LOW	replay/build.go	201	}	COMMENT
LOW	replay/materials.go	21		COMMENT
LOW	replay/materials.go	41	}	COMMENT
LOW	replay/materials.go	181	return r != nil && (len(r.stores) > 0 \|\| len(r.overrides) > 0)	COMMENT
LOW	replay/materials.go	201		COMMENT
LOW	replay/materials.go	221	// and not reachable via the sentinel produce MaterialNotFoundError. The	COMMENT
LOW	replay/materials.go	421	// 1. Scanning every per-platform snapshot index's materials-manifest	COMMENT
LOW	replay/subject.go	41	// reads the exported fields, but the kind guides error messages.	COMMENT
LOW	replay/subject.go	61	Descriptor ocispecs.Descriptor	COMMENT
LOW	replay/subject.go	201	}	COMMENT
LOW	replay/subject.go	401	return out	COMMENT
LOW	replay/snapshot.go	41	// withMediaTypeKeyPrefix registers ref-key prefixes for non-standard media	COMMENT
LOW	replay/snapshot.go	61	// (descriptor, provider) pair. Required when IncludeMaterials is true.	COMMENT
LOW	dap/thread.go	221	entrypoint.parent = t.determineParent(op)	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	cmd/buildx/main.go	34	// Use custom grpc codec to utilize vtprotobuf	COMMENT

Slop Phrases2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	bake/compose.go	424	// don't forget to update documentation if you add a new field:	COMMENT
LOW	commands/bake.go	233	// don't forget to update documentation if you add a new	COMMENT

Verbosity Indicators1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	util/gitutil/path.go	14	// On WSL2 we need to check if the current working directory is mounted on	COMMENT

TODO Padding1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	util/otelutil/span.go	123	TraceState string // TODO: implement, currently dropped	CODE