AI Slop Code Risk Monitor

ChrisTitusTech/linutil

Name: ChrisTitusTech/linutil — 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).

Chris Titus Tech's Linux Toolbox - Linutil is a distro-agnostic toolbox designed to simplify everyday Linux tasks.

2.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for ChrisTitusTech/linutil, a Shell project with 5,343 GitHub stars. SynthScan examined 24,865 lines of code across 277 source files, recording 26 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 2.1 (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.1

Adjusted Signal

2.1

Raw Pattern Score

100%

Time Factor

2026-11-01

Last Push

5.3K

Stars

Shell

Language

24.9K

Lines of Code

277

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

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

Which changes need focused human review? 26 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 9LOW 17

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 26 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.

Redundant / Tautological Comments16 hits · 27 pts

Severity	File	Line	Snippet	Context
LOW	preview.sh	8	# Check if VHS is installed	COMMENT
LOW	preview.sh	15	# Check if linutil binary exists	COMMENT
LOW	core/tabs/common-script.sh	183	## Check if the current directory is writable.	COMMENT
LOW	core/tabs/utils/wifi-control.sh	31	# Check if NetworkManager service is running	COMMENT
LOW	core/tabs/utils/auto-mount.sh	13	# Check if the input is valid	COMMENT
LOW	core/tabs/utils/ssh.sh	5	# Check if ~/.ssh/config exists, if not, create it	COMMENT
LOW	core/tabs/utils/service-control.sh	298	# Check if User= exists and append username if needed	COMMENT
LOW	…re/tabs/system-setup/desktop-environments-uninstall.sh	5	# Check if WM/DE is installed	COMMENT
LOW	core/tabs/system-setup/fedora/fedora-btrfs-assistant.sh	98	# Check if the grub-btrfs dir exists before attempting to clone into it.	COMMENT
LOW	…system-setup/fedora/nvidia-proprietary-driver-setup.sh	31	# Verify if the repository is enabled	COMMENT
LOW⚡	core/tabs/system-setup/arch/chaotic-aur-setup.sh	8	# Check if Chaotic-AUR is already installed	COMMENT
LOW⚡	core/tabs/system-setup/arch/chaotic-aur-setup.sh	10	# Print message indicating Chaotic-AUR is being installed	COMMENT
LOW⚡	core/tabs/system-setup/arch/chaotic-aur-setup.sh	19	# Print message indicating Chaotic-AUR has been installed and enabled	COMMENT
LOW⚡	core/tabs/system-setup/arch/chaotic-aur-setup.sh	22	# Print message indicating Chaotic-AUR is already installed	COMMENT
LOW	core/tabs/applications-setup/mybash-setup.sh	28	# Check if the dir exists before attempting to clone into it.	COMMENT
LOW	core/tabs/applications-setup/developer-tools/neovim.sh	8	# Check if the dir exists before attempting to clone into it.	COMMENT

Self-Referential Comments9 hits · 23 pts

Severity	File	Line	Snippet	Context
MEDIUM	core/tabs/utils/ollama.sh	133	# Create the Modelfile	COMMENT
MEDIUM	core/tabs/utils/ollama.sh	147	# Create the model in Ollama	STRING
MEDIUM	core/tabs/utils/service-control.sh	139	# Create the service unit file	COMMENT
MEDIUM	core/tabs/utils/service-control.sh	142	# Create the service file with conditionals for optional fields	COMMENT
MEDIUM	core/tabs/utils/service-control.sh	293	# Create the systemd service file path	COMMENT
MEDIUM	core/tabs/utils/samba-ssh-setup.sh	95	# Create the shared directory if it doesn't exist	COMMENT
MEDIUM	core/tabs/utils/ramalama.sh	198	# Create the Modelfile	COMMENT
MEDIUM	core/tabs/utils/ramalama.sh	212	# Create the model in ramalama	STRING
MEDIUM	core/tabs/applications-setup/browsers/google-chrome.sh	84	# Create an empty directory and make it read-only	COMMENT

Over-Commented Block1 hit · 1 pts

Severity	File	Line	Snippet	Context
LOW	core/tabs/gaming/common-steam-script.sh	1	#!/bin/sh	COMMENT