AI Slop Code Risk Monitor

hashicorp/go-plugin

Name: hashicorp/go-plugin — 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).

Golang plugin system over RPC.

2.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for hashicorp/go-plugin, a Go project with 6,115 GitHub stars. SynthScan examined 14,000 lines of code across 102 source files, recording 31 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.6 (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.6

Adjusted Signal

2.6

Raw Pattern Score

100%

Time Factor

2026-10-12

Last Push

6.1K

Stars

Language

14.0K

Lines of Code

102

Files

Pattern Hits

2026-10-31

Scan Date

0.01

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

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

Hallucinated Dependency & Supply Chain Risk 0.7/100 · LOW

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

Agent Over-Engineering Ratio 2.5/100 · LOW

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

PR Review Velocity Impact 12.7/100 · LOW

Which changes need focused human review? 31 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 1MEDIUM 1LOW 29

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 31 distinct pattern matches across 4 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 Block27 hits · 27 pts

Severity	File	Line	Snippet	Context
LOW	server.go	21	"strings"	COMMENT
LOW	server.go	41	type HandshakeConfig struct {	COMMENT
LOW	server.go	61	// ServeConfig configures what sorts of plugins are served.	COMMENT
LOW	server.go	81	// be for TLS if set. You may modify the input slice.	COMMENT
LOW	server.go	101	// * Connection information will not be sent to stdout	COMMENT
LOW	server.go	221	return protoVersion, protoType, pluginSet	COMMENT
LOW	protocol.go	21	// protocols to be servers.	COMMENT
LOW	discover.go	1	// Copyright IBM Corp. 2016, 2025	COMMENT
LOW	client.go	61	ErrSecureConfigNoHash = errors.New("no hash implementation provided")	COMMENT
LOW	client.go	141	// that configuration must not be modified again.	COMMENT
LOW	client.go	161	// Reattach is configuration for reattaching to an existing plugin process	COMMENT
LOW	client.go	181	// plugin package or not. If true, then by calling CleanupClients,	COMMENT
LOW	client.go	201	// SyncStdout, SyncStderr can be set to override the	COMMENT
LOW	client.go	221	// Logger is the logger that the client will used. If none is provided,	COMMENT
LOW	client.go	241	// Setting AutoMTLS to true implies that the server must support the	COMMENT
LOW	client.go	261	// server (i.e. plugin) side of gRPC broker multiplexing.	COMMENT
LOW	client.go	281	// this group, and set them as group-writable. Can be a name or gid. The	COMMENT
LOW	client.go	301	ProtocolVersion int	COMMENT
LOW	plugin.go	21		COMMENT
LOW	rpc_client.go	101	}	COMMENT
LOW	mux_broker.go	21	// streams on top of a single connection between the plugin process and the	COMMENT
LOW	testing.go	21	// test functions	COMMENT
LOW	grpc_broker.go	241		COMMENT
LOW	internal/grpcmux/grpc_server_muxer.go	21	// GRPCMuxer interface for multiplexing multiple gRPC broker connections over	COMMENT
LOW	internal/grpcmux/grpc_muxer.go	1	// Copyright IBM Corp. 2016, 2025	COMMENT
LOW	internal/grpcmux/grpc_muxer.go	21	// Enabled determines whether multiplexing should be used. It saves users	COMMENT
LOW	examples/basic/shared/greeter_interface.go	41	return nil	COMMENT

Empty Error Handlers1 hit · 5 pts

Severity	File	Line	Snippet	Context
HIGH	examples/grpc/plugin-python/plugin.py	105	except KeyboardInterrupt:	CODE

Dead Code1 hit · 2 pts

Severity	File	Line	Snippet	Context
MEDIUM	examples/grpc/plugin-python/plugin.py	76		CODE

Fake / Example Data2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	examples/streaming/main.go	75	err = streamer.Write(ctx, []byte("Lorem ipsum dolor sit amet"))	CODE
LOW	examples/streaming/main.go	75	err = streamer.Write(ctx, []byte("Lorem ipsum dolor sit amet"))	CODE