AI Slop Code Risk Monitor

etcd-io/bbolt

Name: etcd-io/bbolt — 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).

An embedded key/value database for Go.

2.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for etcd-io/bbolt, a Go project with 9,793 GitHub stars. SynthScan examined 28,457 lines of code across 151 source files, recording 41 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 2.0 (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.0

Adjusted Signal

2.0

Raw Pattern Score

100%

Time Factor

2026-10-16

Last Push

9.8K

Stars

Language

28.5K

Lines of Code

151

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

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

Hallucinated Dependency & Supply Chain Risk 1.7/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 8.4/100 · LOW

Which changes need focused human review? 41 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 1HIGH 0MEDIUM 0LOW 40

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 41 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 Block28 hits · 28 pts

Severity	File	Line	Snippet	Context
LOW	db.go	21	// FreelistType is the type of the freelist backend	COMMENT
LOW	db.go	41	// flag has a large performance impact so it should only be used for	COMMENT
LOW	db.go	61		COMMENT
LOW	db.go	81		COMMENT
LOW	db.go	101		COMMENT
LOW	db.go	741		COMMENT
LOW	db.go	961	}	COMMENT
LOW	db.go	1321	// Options represents the options that can be set when opening a database.	COMMENT
LOW	db.go	1341	// The alternative one is using hashmap, it is faster in almost all circumstances	COMMENT
LOW	db.go	1361	//	COMMENT
LOW	tx_check.go	1	package bbolt	COMMENT
LOW	cursor_test.go	981		COMMENT
LOW	tx.go	121		COMMENT
LOW	tx.go	381	// This function exists for backwards compatibility.	COMMENT
LOW	tx.go	701	// DEPRECATED: Use GetPageCount() or IncPageCount()	COMMENT
LOW	errors.go	1	package bbolt	COMMENT
LOW	errors.go	21	// Deprecated: Use the error variables defined in the bbolt/errors package.	COMMENT
LOW	errors.go	41		COMMENT
LOW	errors.go	61		COMMENT
LOW	errors.go	81		COMMENT
LOW	errors.go	101		COMMENT
LOW	tests/failpoint/db_failpoint_test.go	181		COMMENT
LOW	tests/dmflakey/dmflakey.go	161	// 0 imgSize flakey <dev path> <offset> <up interval> <down interval> [<num_features> [<feature arguments>]]	COMMENT
LOW	tests/dmflakey/dmflakey.go	181	}	COMMENT
LOW	tests/dmflakey/dmflakey.go	201	// Optional:	COMMENT
LOW	tests/dmflakey/dmflakey.go	241	// <down interval>: Number of seconds device returns errors.	COMMENT
LOW	internal/surgeon/surgeon.go	21	}	COMMENT
LOW	internal/common/unsafe.go	21	// subslice to begin after the base address, with an optional offset,	COMMENT

Hallucination Indicators1 hit · 10 pts

Severity	File	Line	Snippet	Context
CRITICAL	node.go	492	n.bucket.tx.db.freelist.Free(n.bucket.tx.meta.Txid(), n.bucket.tx.page(n.pgid))	CODE

Verbosity Indicators6 hits · 9 pts

Severity	File	Line	Snippet	Context
LOW	cursor_test.go	77	// Step 1: verify next	COMMENT
LOW	cursor_test.go	90	// Step 2: verify prev	COMMENT
LOW	cursor_test.go	103	// Step 3: verify next again	COMMENT
LOW	cursor_test.go	118	// Step 1: verify prev	COMMENT
LOW	cursor_test.go	131	// Step 2: verify next	COMMENT
LOW	cursor_test.go	144	// Step 3: verify prev again	COMMENT

Structural Annotation Overuse6 hits · 9 pts

Severity	File	Line	Snippet	Context
LOW	cursor_test.go	77	// Step 1: verify next	COMMENT
LOW	cursor_test.go	90	// Step 2: verify prev	COMMENT
LOW	cursor_test.go	103	// Step 3: verify next again	COMMENT
LOW	cursor_test.go	118	// Step 1: verify prev	COMMENT
LOW	cursor_test.go	131	// Step 2: verify next	COMMENT
LOW	cursor_test.go	144	// Step 3: verify prev again	COMMENT