AI Slop Code Risk Monitor

zeromicro/go-zero

Name: zeromicro/go-zero — 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).

A cloud-native Go microservices framework with cli tool for productivity.

0.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for zeromicro/go-zero, a Go project with 33,417 GitHub stars. SynthScan examined 175,961 lines of code across 1139 source files, recording 34 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.2 (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.2

Adjusted Signal

0.2

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

33.4K

Stars

Language

176.0K

Lines of Code

1.1K

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

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

Are imports declared and package/API names verified? 2 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.0/100 · LOW

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

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 34 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	zrpc/resolver/internal/targets/endpoints.go	21	// GetHosts returns the comma-separated etcd hosts from the target URL.	COMMENT
LOW	tools/goctl/config/config.go	21	//go:embed default.yaml	COMMENT
LOW	tools/goctl/model/sql/template/template.go	21	// Types defines a template for types in model.	COMMENT
LOW	tools/goctl/model/sql/template/template.go	81	//	COMMENT
LOW	tools/goctl/model/sql/template/template.go	101	//	COMMENT
LOW	tools/goctl/model/sql/template/template.go	121	//	COMMENT
LOW	tools/goctl/rpc/generator/gen.go	21	ProtoGenGoDir string	COMMENT
LOW	tools/goctl/gateway/conf.yml	1	Name: gateway-example # gateway name	COMMENT
LOW	core/logx/config.go	1	package logx	COMMENT
LOW	core/logx/config.go	21	// Level represents the log level, default is `info`.	COMMENT
LOW	core/logx/writer.go	21	// Writer is the interface for writing logs.	COMMENT
LOW	core/breaker/breaker.go	21	type (	COMMENT
LOW	core/breaker/breaker.go	41	// If a panic occurs in the request, the Breaker handles it as an error	COMMENT
LOW	core/stores/cache/cache.go	21	// DelCtx deletes cached values with keys.	COMMENT
LOW	core/stores/redis/conf.go	21	Type string `json:",default=node,options=node\|cluster"`	COMMENT
LOW	core/stores/redis/redisblockingnode.go	21	//	COMMENT
LOW	core/stores/redis/redis.go	261	// Blpop uses passed in redis connection to execute blocking queries.	COMMENT
LOW	core/stores/redis/redis.go	281	func (s *Redis) Blpop(node RedisNode, key string) (string, error) {	COMMENT
LOW	core/stores/redis/redis.go	1921	// XInfoStreamCtx is the context-aware version of XInfoStream.	COMMENT
LOW	core/stores/redis/redis.go	1941	// if err != nil {	COMMENT
LOW	core/stores/mon/collection.go	81	// FindOneAndDelete returns at most one document that matches the filter. If the filter	COMMENT
LOW	core/stores/mon/collection.go	601	// Find finds the documents matching the provided filter.	COMMENT
LOW	mcp/types.go	81	// tool := &mcp.Tool{	COMMENT
LOW	.github/workflows/codeql-analysis.yml	1	# For most projects, this workflow file will not need changing; you simply need	COMMENT
LOW	rest/server_test.go	801	assert.Nil(t, err)	COMMENT
LOW	rest/chain/chain.go	41	// c.Append(m3, m4)	COMMENT
LOW	rest/chain/chain.go	61	// is equivalent to:	COMMENT

Example Usage Blocks3 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	core/stores/redis/redisblockingnode.go	26	// Example usage:	COMMENT
LOW	core/stores/redis/redis.go	267	// Example usage:	COMMENT
LOW	core/stores/redis/redis.go	1938	// Example usage:	COMMENT

Verbosity Indicators2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	tools/goctl/pkg/parser/api/parser/parser.go	1700	// The following code block are experimental, do not call it out of unit test.	COMMENT
LOW	rest/handler/timeouthandler.go	228	// The purpose of this function is to provide more helpful error messages.	COMMENT

Fake / Example Data2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	core/stores/cache/cachenode.go	28	var errPlaceholder = errors.New("placeholder")	CODE
LOW	core/stores/sqlx/stmt_test.go	17	var errMockedPlaceholder = errors.New("placeholder")	CODE