AI Slop Code Risk Monitor

micro-editor/micro

Name: micro-editor/micro — 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 modern and intuitive terminal-based text editor

2.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for micro-editor/micro, a Go project with 29,804 GitHub stars. SynthScan examined 37,807 lines of code across 293 source files, recording 40 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 2.6 (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.6

Adjusted Signal

2.6

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

29.8K

Stars

Language

37.8K

Lines of Code

293

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

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

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

PR Review Velocity Impact 9.8/100 · LOW

Which changes need focused human review? 40 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 19LOW 21

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 40 distinct pattern matches across 3 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.

Decorative Section Separators18 hits · 75 pts

Severity	File	Line	Snippet	Context
MEDIUM	runtime/syntax/b.yaml	9	# -------------------------	COMMENT
MEDIUM	runtime/syntax/b.yaml	11	# -------------------------	COMMENT
MEDIUM	runtime/syntax/b.yaml	23	# -------------------------	COMMENT
MEDIUM	runtime/syntax/b.yaml	25	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	44	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	47	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	51	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	53	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	57	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	59	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	62	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	64	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	70	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	73	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	79	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	81	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	84	# -------------------------	COMMENT
MEDIUM⚡	runtime/syntax/b.yaml	86	# -------------------------	COMMENT

Over-Commented Block21 hits · 21 pts

Severity	File	Line	Snippet	Context
LOW	cmd/micro/micro_test.go	241		COMMENT
LOW	runtime/syntax/terraform.yaml	1	#	COMMENT
LOW	runtime/syntax/terraform.yaml	21		COMMENT
LOW	runtime/syntax/sh.yaml	1	filetype: shell	COMMENT
LOW	runtime/syntax/octave.yaml	1	# References	COMMENT
LOW	runtime/syntax/PowerShell.yaml	1	# PowerShell syntax highlighting file for micro - https://micro-editor.github.io/	COMMENT
LOW	runtime/syntax/PowerShell.yaml	21	# - constant.string.char:	COMMENT
LOW	runtime/syntax/PowerShell.yaml	41		COMMENT
LOW	runtime/syntax/b.yaml	61		COMMENT
LOW	runtime/syntax/jsonnet.yaml	61	# block string	COMMENT
LOW	internal/util/util.go	701	// temporary file first.	COMMENT
LOW	internal/shell/shell.go	121	signal.Stop(c)	COMMENT
LOW	internal/action/infocomplete.go	301	completions := make([]string, len(suggestions))	COMMENT
LOW	internal/action/infocomplete.go	321	// completions := make([]string, len(suggestions))	COMMENT
LOW	internal/action/infopane.go	141	if !more {	COMMENT
LOW	internal/action/keytree.go	161	n = newNode	COMMENT
LOW	internal/action/bufpane.go	201	// The BufPane connects the buffer and the window	COMMENT
LOW	internal/action/bufpane.go	221	// pressed, to determine mouse release and mouse drag events.	COMMENT
LOW	internal/action/bufpane.go	601	action(h)	COMMENT
LOW	internal/buffer/line_array.go	361	// Locks the whole LineArray	COMMENT
LOW	internal/buffer/cursor.go	21	Loc	COMMENT

Self-Referential Comments1 hit · 3 pts

Severity	File	Line	Snippet	Context
MEDIUM	runtime/syntax/asm.yaml	7	# This file is made mainly for NASM assembly	COMMENT