AI Slop Code Risk Monitor

charmbracelet/bubbletea

Name: charmbracelet/bubbletea — 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 powerful little TUI framework 🏗

3.4 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for charmbracelet/bubbletea, a Go project with 45,566 GitHub stars. SynthScan examined 17,693 lines of code across 173 source files, recording 57 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 3.4 (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.

3.4

Adjusted Signal

3.4

Raw Pattern Score

100%

Time Factor

2026-10-28

Last Push

45.6K

Stars

Language

17.7K

Lines of Code

173

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

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

Which changes need focused human review? 57 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 1LOW 56

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 57 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 Block54 hits · 54 pts

Severity	File	Line	Snippet	Context
LOW	raw.go	1	package tea	COMMENT
LOW	raw.go	21	// for _, attr := range msg {	COMMENT
LOW	color.go	41	// String returns the hex representation of the color.	COMMENT
LOW	color.go	61	// return RequestBackgroundColor	COMMENT
LOW	options.go	41	// Note that with input disabled, no terminal query is ever sent, since the	COMMENT
LOW	options.go	101	// This can be useful if you want to use the Bubble Tea framework for a non-TUI	COMMENT
LOW	options.go	121	// func filter(m tea.Model, msg tea.Msg) tea.Msg {	COMMENT
LOW	tea.go	61		COMMENT
LOW	tea.go	81		COMMENT
LOW	tea.go	101	// breaking the unidirectional data flow of Bubble Tea.	COMMENT
LOW	tea.go	121	// }	COMMENT
LOW	tea.go	141	// WindowTitle sets the terminal window title. Support depends on the	COMMENT
LOW	tea.go	161	ProgramStatus *ProgramStatus	COMMENT
LOW	tea.go	181	// Note that while most terminals and multiplexers support focus reporting,	COMMENT
LOW	tea.go	201	// receive a [KeyboardEnhancementsMsg] that indicates which features are	COMMENT
LOW	tea.go	221	// Example:	COMMENT
LOW	tea.go	241	// case tea.KeyReleaseMsg:	COMMENT
LOW	tea.go	261	ReportEventTypes bool	COMMENT
LOW	tea.go	281	}	COMMENT
LOW	tea.go	301	// MouseModeNone disables mouse events.	COMMENT
LOW	tea.go	461	disableCatchPanics bool	COMMENT
LOW	tea.go	481	// return nil	COMMENT
LOW	tea.go	501	// initialModel is the initial model for the program and is the only	COMMENT
LOW	tea.go	581	// QuitMsg signals that the program should quit. You can send a [QuitMsg] with	COMMENT
LOW	tea.go	1221		COMMENT
LOW	screen.go	21		COMMENT
LOW	screen.go	41	// switch msg := msg.(type) {	COMMENT
LOW	exec.go	21	// For non-interactive i/o you should use a Cmd (that is, a tea.Cmd).	COMMENT
LOW	exec.go	41	// cmd := ExecProcess(c, func(err error) Msg {	COMMENT
LOW	key.go	201	// convenient and readable to use this method when matching against keys.	COMMENT
LOW	key.go	221	}	COMMENT
LOW	key.go	261		COMMENT
LOW	key.go	281	//	COMMENT
LOW	key.go	301	// 'A', '1', '!', etc.).	COMMENT
LOW	key.go	321	//	COMMENT
LOW	key.go	341	// Console API.	COMMENT
LOW	key.go	361	// - alt	COMMENT
LOW	mouse.go	41	MouseButton11 = uv.MouseButton11	COMMENT
LOW	mouse.go	61	// case MouseMsg:	COMMENT
LOW	cursed_renderer.go	181	// so that we can restore them when we start the renderer again. This is	COMMENT
LOW	cursed_renderer.go	421	// the program exits.	COMMENT
LOW	cursed_renderer.go	561	// 1. Synchronized output updates are supported. In this case, we want to	COMMENT
LOW	programstatus.go	41		COMMENT
LOW	termcap.go	1	package tea	COMMENT
LOW	termcap.go	21	//	COMMENT
LOW	environ.go	1	package tea	COMMENT
LOW	keyboard.go	1	package tea	COMMENT
LOW	keyboard.go	21	// }	COMMENT
LOW	commands.go	61	// the entire specified duration. For example, if we're ticking for one minute	COMMENT
LOW	commands.go	81	// func tickEvery() Cmd {	COMMENT
LOW	commands.go	121	// a message containing the time at which the tick occurred.	COMMENT
LOW	commands.go	141	// func (m model) Init() (Model, Cmd) {	COMMENT
LOW	clipboard.go	61	// readPrimaryClipboardMsg is an internal message used to read the primary	COMMENT
LOW	examples/progress-static/main.go	1	package main	COMMENT

AI Slop Vocabulary1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	examples/keyboard-enhancements/main.go	41	// This allows for more nuanced input handling in terminal applications.	COMMENT

Example Usage Blocks1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	options.go	14	// Example usage:	COMMENT

Slop Phrases1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	logging.go	15	// Don't forget to close the file when you're done with it.	COMMENT