AI Slop Code Risk Monitor

urfave/cli

Name: urfave/cli — 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 declarative, simple, fast, and fun package for building command line tools in Go

0.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for urfave/cli, a Go project with 24,306 GitHub stars. SynthScan examined 44,439 lines of code across 162 source files, recording 37 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 0.8 (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.8

Adjusted Signal

0.8

Raw Pattern Score

100%

Time Factor

2026-10-29

Last Push

24.3K

Stars

Language

44.4K

Lines of Code

162

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

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

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

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 37 distinct pattern matches across 1 syntactic category. 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 Block37 hits · 37 pts

Severity	File	Line	Snippet	Context
LOW	godoc-current.txt	481	Description string `json:"description"`	COMMENT
LOW	godoc-current.txt	501	EnableShellCompletion bool `json:"-"`	COMMENT
LOW	godoc-current.txt	521	// Execute this function if the proper command cannot be found	COMMENT
LOW	godoc-current.txt	541	Writer io.Writer `json:"-"`	COMMENT
LOW	godoc-current.txt	561	// DisableSliceFlagSeparator is used to disable SliceFlagSeparator, the default is false.	COMMENT
LOW	godoc-current.txt	581	// cli.go uses text/template to render templates. You can	COMMENT
LOW	godoc-current.txt	1361	// whether this group is required	COMMENT
LOW	command.go	21	// accepts a string slice of arguments such as os.Args. A given	COMMENT
LOW	command.go	41	// The category the command is part of	COMMENT
LOW	command.go	61	ShellComplete ShellCompleteFunc `json:"-"`	COMMENT
LOW	command.go	81	// Execute this function when an invalid flag is accessed from the context	COMMENT
LOW	command.go	101	// returned to the caller. If no function is provided, HandleExitCoder is used as the	COMMENT
LOW	command.go	121	// MapFlagKeyValueSeparator is used to customize the separator for MapFlag, the default is "=".	COMMENT
LOW	command.go	141	PrefixMatchCommands bool `json:"prefixMatchCommands"`	COMMENT
LOW	command.go	161	categories CommandCategories	COMMENT
LOW	flag_impl.go	141		COMMENT
LOW	examples_test.go	101	Description: "This is how we describe describeit the function",	COMMENT
LOW	examples_test.go	121	// AUTHORS:	COMMENT
LOW	examples_test.go	161	// This is how we describe describeit the function	COMMENT
LOW	examples_test.go	201	// NAME:	COMMENT
LOW	flag_mutex.go	1	package cli	COMMENT
LOW	help_notemplate.go	21	RootCommandHelpTemplate = "root"	COMMENT
LOW	cli.go	1	// Package cli provides a minimal framework for creating and organizing command line	COMMENT
LOW	funcs.go	21	// If non-nil, it is called before the command's After and Action functions.	COMMENT
LOW	help.go	21	// Prints help for the Command with custom template function.	COMMENT
LOW	help.go	81	func helpCommandAction(ctx context.Context, cmd *Command) error {	COMMENT
LOW	help.go	101	// # matches a child command; otherwise ignore it	COMMENT
LOW	help.go	541	// this function tries to find the max width of the names column	COMMENT
LOW	errors.go	161		COMMENT
LOW	testdata/godoc-v3.x.txt	481	Description string `json:"description"`	COMMENT
LOW	testdata/godoc-v3.x.txt	501	EnableShellCompletion bool `json:"-"`	COMMENT
LOW	testdata/godoc-v3.x.txt	521	// Execute this function if the proper command cannot be found	COMMENT
LOW	testdata/godoc-v3.x.txt	541	Writer io.Writer `json:"-"`	COMMENT
LOW	testdata/godoc-v3.x.txt	561	// DisableSliceFlagSeparator is used to disable SliceFlagSeparator, the default is false.	COMMENT
LOW	testdata/godoc-v3.x.txt	581	// cli.go uses text/template to render templates. You can	COMMENT
LOW	testdata/godoc-v3.x.txt	1361	// whether this group is required	COMMENT
LOW	testdata/empty.yml	1	# empty file	COMMENT