AI Slop Code Risk Monitor

qemus/qemu

Name: qemus/qemu — Shell 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).

QEMU in a Docker container.

3.8 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for qemus/qemu, a Shell project with 2,173 GitHub stars. SynthScan examined 22,091 lines of code across 78 source files, recording 41 pattern matches distributed across 10 syntactic categories. The legacy adjusted pattern signal is 3.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.

3.8

Adjusted Signal

3.8

Raw Pattern Score

100%

Time Factor

2026-10-05

Last Push

2.2K

Stars

Shell

Language

22.1K

Lines of Code

Files

Pattern Hits

2026-10-31

Scan Date

0.04

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

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 13.4/100 · LOW

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

PR Review Velocity Impact 16.9/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 0HIGH 3MEDIUM 13LOW 25

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 10 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 Separators8 hits · 33 pts

Severity	File	Line	Snippet	Context
MEDIUM⚡	src/balloon.py	212	# ==========================================================	COMMENT
MEDIUM⚡	src/balloon.py	214	# ==========================================================	COMMENT
MEDIUM⚡	src/balloon.py	290	# ==========================================================	COMMENT
MEDIUM⚡	src/balloon.py	292	# ==========================================================	COMMENT
MEDIUM⚡	src/balloon.py	733	# ==========================================================	COMMENT
MEDIUM⚡	src/balloon.py	735	# ==========================================================	COMMENT
MEDIUM	src/balloon.py	29	# ==========================================================	COMMENT
MEDIUM	src/balloon.py	31	# ==========================================================	COMMENT

Empty Error Handlers3 hits · 15 pts

Severity	File	Line	Snippet	Context
HIGH	src/audio.py	18	except FileNotFoundError:	CODE
HIGH	src/audio.py	42	except OSError:	CODE
HIGH	src/balloon.py	343	except OSError:	CODE

Excessive Try-Catch Wrapping13 hits · 13 pts

Severity	File	Line	Snippet	Context
MEDIUM	src/balloon.py	340	def _on_cgroup_change(self) -> None:	CODE
LOW⚡	src/balloon.py	206	except Exception as e:	CODE
LOW⚡	src/balloon.py	286	except Exception as e:	CODE
LOW⚡	src/balloon.py	730	except Exception as e:	CODE
LOW	src/balloon.py	46	except Exception as e:	CODE
LOW	src/balloon.py	90	except Exception as e:	CODE
LOW	src/balloon.py	110	except Exception as e:	CODE
LOW	src/balloon.py	239	except Exception as e:	CODE
LOW	src/balloon.py	403	except Exception as e:	CODE
LOW	src/balloon.py	414	except Exception as e:	CODE
LOW	src/balloon.py	705	except Exception as e:	CODE
LOW	src/balloon.py	715	except Exception as e:	CODE
LOW	src/balloon.py	821	except Exception as e:	CODE

Self-Referential Comments4 hits · 12 pts

Severity	File	Line	Snippet	Context
MEDIUM	src/network.sh	765	# Create the necessary file structure for /dev/vhost-net	COMMENT
MEDIUM	src/network.sh	772	# Create a macvtap network for the VM guest	COMMENT
MEDIUM	src/network.sh	1029	# Create a bridge with a static IP for the VM guest	COMMENT
MEDIUM	src/network.sh	1790	# Create the necessary file structure for /dev/net/tun	COMMENT

Redundant / Tautological Comments3 hits · 4 pts

Severity	File	Line	Snippet	Context
LOW	src/network.sh	1073	# Set tap to the bridge created	COMMENT
LOW	src/network.sh	2074	# Check if host exposes the bridge-nf sysctl	COMMENT
LOW	src/balloon.py	167	# Check if this block matches one of our expected remaining QMP memory backends.	COMMENT

Deep Nesting5 hits · 2 pts

Severity	File	Line	Context
LOW	src/balloon.py	50	CODE
LOW	src/balloon.py	95	CODE
LOW	src/balloon.py	145	CODE
LOW	src/balloon.py	461	CODE
LOW	src/balloon.py	644	CODE

Modern Structural Boilerplate2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	src/balloon.py	318	def _setup_cgroup_watch(self) -> None:	CODE
LOW	src/balloon.py	605	async def _update_balloon(self) -> None:	CODE

Over-Commented Block1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	web/vnc/core/util/cursor.js	161		COMMENT

Hyper-Verbose Identifiers1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	src/balloon.py	145	async def _get_host_qemu_guest_mem_rss(qmp: QMPClient, qemu_pid: int) -> Optional[int]:	CODE

Unused Imports1 hit · 0 pts

Severity	File	Line	Snippet	Context
LOW	src/balloon.py	3		CODE