AI Slop Code Risk Monitor

junegunn/fzf

Name: junegunn/fzf — 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).

:cherry_blossom: A command-line fuzzy finder

0.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for junegunn/fzf, a Go project with 83,876 GitHub stars. SynthScan examined 52,441 lines of code across 135 source files, recording 28 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 0.7 (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.7

Adjusted Signal

0.7

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

83.9K

Stars

Language

52.4K

Lines of Code

135

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

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

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

PR Review Velocity Impact 3.6/100 · LOW

Which changes need focused human review? 28 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 5LOW 23

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 28 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 Block21 hits · 21 pts

Severity	File	Line	Snippet	Context
LOW	bin/fzf-preview.sh	61	if [[ $KITTY_WINDOW_ID ]] \|\| [[ $GHOSTTY_RESOURCES_DIR ]] && command -v kitten > /dev/null; then	COMMENT
LOW	shell/completion.bash	1	# ____ ____	COMMENT
LOW	shell/completion.bash	21	# -a -not -path "$1" -print 2> /dev/null \| command sed 's@^\./@@'	COMMENT
LOW	shell/completion.bash	521	# desired sorting and with any duplicates removed, to standard output.	COMMENT
LOW	shell/key-bindings.bash	1	# ____ ____	COMMENT
LOW	shell/completion.zsh	1	# ____ ____	COMMENT
LOW	shell/completion.zsh	21	# careful when you change it.	COMMENT
LOW	shell/completion.zsh	61		COMMENT
LOW	shell/completion.zsh	81	#	COMMENT
LOW	shell/completion.zsh	261	}	COMMENT
LOW	shell/key-bindings.zsh	1	# ____ ____	COMMENT
LOW	src/terminal.go	1801	if !hasInputWindow {	COMMENT
LOW	src/terminal.go	4181	}	COMMENT
LOW	src/terminal.go	6661	// T1 T2 (good) \| T1 T2 (bad)	COMMENT
LOW	src/tmux.go	21	// TMUX_PANE is not set when fzf is not started from within a pane	COMMENT
LOW	src/tmux.go	141	// that they are in place no matter how quickly the command exits.	COMMENT
LOW	src/tui/tcell_test.go	21		COMMENT
LOW	src/algo/indexbyte2_arm64.go	1	//go:build arm64	COMMENT
LOW	src/algo/indexbyte2_amd64.go	21	// or -1 if neither is present. Uses AVX2 when available, SSE2 otherwise.	COMMENT
LOW	src/algo/fastpath_equiv_test.go	1	package algo	COMMENT
LOW	src/algo/algo.go	121	// 8 characters, which is approximately the average length of the words found	COMMENT

Decorative Section Separators4 hits · 12 pts

Severity	File	Line	Snippet	Context
MEDIUM	test/lib/common.sh	16	# ---------------	COMMENT
MEDIUM	test/lib/common.sh	20	# ------------	COMMENT
MEDIUM	shell/key-bindings.bash	18	# ------------	COMMENT
MEDIUM	shell/key-bindings.zsh	16	# ------------	COMMENT

Redundant / Tautological Comments2 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	shell/completion.zsh	426	# Check if at least one completion system (old or new) is active.	COMMENT
LOW	shell/update.sh	30	# Check if --check is in ARGV	COMMENT

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	shell/completion.zsh	433	# Create a completion widget to access the 'words' array (man zshcompwid)	COMMENT