AI Slop Code Risk Monitor

zsh-users/zsh

Name: zsh-users/zsh — C 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).

Mirror of the Z shell source code repository.

0.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for zsh-users/zsh, a C project with 4,326 GitHub stars. SynthScan examined 157,624 lines of code across 121 source files, recording 151 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 0.9 (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.9

Adjusted Signal

0.9

Raw Pattern Score

100%

Time Factor

2026-10-25

Last Push

4.3K

Stars

Language

157.6K

Lines of Code

121

Files

151

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

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

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

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

Over-Commented Block149 hits · 133 pts

Severity	File	Line	Snippet	Context
LOW	Test/ztst.zsh	1	#!/bin/zsh -f	COMMENT
LOW	Src/mkmakemod.sh	1	#!/bin/sh	COMMENT
LOW	Src/mkmakemod.sh	21	# moddeps modules on which this module depends (default none)	COMMENT
LOW	Src/mkmakemod.sh	41	# be recreated if any of the dependency .mdh files changes, or if any of	COMMENT
LOW	Src/math.c	101	#define OP_A2 0x0004	COMMENT
LOW	Src/math.c	121	#define DIV 12	COMMENT
LOW	Src/math.c	141	#define MULEQ 32	COMMENT
LOW	Src/lex.c	381	#define LX1_OTHER 15	COMMENT
LOW	Src/hashtable.h	41	#define BIN_CONTINUE 7	COMMENT
LOW	Src/hashtable.h	61	#define BIN_COMMAND 27	COMMENT
LOW	Src/init.c	1041	# define FPATH_NEEDS_INIT 1	COMMENT
LOW	Src/zsh_system.h	41	/*	COMMENT
LOW	Src/zsh_system.h	81	* This is likely to be harmless everywhere else.	COMMENT
LOW	Src/zsh_system.h	101	# endif	COMMENT
LOW	Src/zsh_system.h	121	# include <unistd.h>	COMMENT
LOW	Src/zsh_system.h	141	#include <signal.h>	COMMENT
LOW	Src/zsh_system.h	161	# ifdef HAVE_NDIR_H	COMMENT
LOW	Src/zsh_system.h	201	# define VA_ALIST_PROTO2(x,y) VA_ALIST2(x,y)	COMMENT
LOW	Src/zsh_system.h	221	# define VA_START(ap,x) va_start(ap);	COMMENT
LOW	Src/zsh_system.h	261	# include <utime.h>	COMMENT
LOW	Src/zsh_system.h	281	#else	COMMENT
LOW	Src/zsh_system.h	301	#endif	COMMENT
LOW	Src/zsh_system.h	321	#ifdef HAVE_FCNTL_H	COMMENT
LOW	Src/zsh_system.h	341	# undef WIFSTOPPED	COMMENT
LOW	Src/zsh_system.h	361	#ifndef WIFSTOPPED	COMMENT
LOW	Src/zsh_system.h	381	* hence the declaration for struct termios is missing */	COMMENT
LOW	Src/zsh_system.h	401		COMMENT
LOW	Src/zsh_system.h	421	/* Posix getpgrp takes no argument, while the BSD version *	COMMENT
LOW	Src/zsh_system.h	461	#endif	COMMENT
LOW	Src/zsh_system.h	481	#endif	COMMENT
LOW	Src/zsh_system.h	501	#endif	COMMENT
LOW	Src/zsh_system.h	521	#endif	COMMENT
LOW	Src/zsh_system.h	541	#endif	COMMENT
LOW	Src/zsh_system.h	561	#define BDIGBUFSIZE ((int)((sizeof(zlong) * 8) + 4))	COMMENT
LOW	Src/zsh_system.h	581		COMMENT
LOW	Src/zsh_system.h	601	#if !defined(S_ISFIFO) && defined(S_IFIFO)	COMMENT
LOW	Src/zsh_system.h	621	#endif	COMMENT
LOW	Src/zsh_system.h	641	# define S_ISDOOR(m) ((void)(m), 0)	COMMENT
LOW	Src/zsh_system.h	661	#ifndef S_ISOFL	COMMENT
LOW	Src/zsh_system.h	681	#endif	COMMENT
LOW	Src/zsh_system.h	701	# define S_IROTH 00004	COMMENT
LOW	Src/zsh_system.h	721	#ifndef S_IWUGO	COMMENT
LOW	Src/zsh_system.h	741	# define R_OK 4	COMMENT
LOW	Src/zsh_system.h	781		COMMENT
LOW	Src/zsh_system.h	801	#ifndef MAILDIR_SUPPORT	COMMENT
LOW	Src/zsh_system.h	821	* complete Unicode conversion between wide characters and multibyte strings.	COMMENT
LOW	Src/zsh_system.h	841	# endif	COMMENT
LOW	Src/zsh_system.h	861	# define USE_GETPWNAM	COMMENT
LOW	Src/zsh_system.h	881	#endif	COMMENT
LOW	Src/zsh_system.h	901	# include <termio.h>	COMMENT
LOW	Src/mem.c	1061	# endif	COMMENT
LOW	Src/mem.c	1161	#define M_SNUM 128	COMMENT
LOW	Src/module.c	1501	#define dlerror() (dlerrstr[0])	COMMENT
LOW	Src/module.c	1541		COMMENT
LOW	Src/module.c	1561	# define STR_SETUP "setup_"	COMMENT
LOW	Src/zsh.h	41	#define ZLONG_MAX LLONG_MAX	COMMENT
LOW	Src/zsh.h	161	#define String ((char) 0x85)	COMMENT
LOW	Src/zsh.h	461	/*	COMMENT
LOW	Src/zsh.h	581	#define addlinknode(X,Y) insertlinknode(X,lastnode(X),Y)	COMMENT
LOW	Src/zsh.h	661	#define COND_NOT 0	COMMENT
89 more matches not shown…

Redundant / Tautological Comments1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	Test/ztst.zsh	182	# Print messages if $ZTST_verbose is non-empty	COMMENT

Verbosity Indicators1 hit · 2 pts

Severity	File	Line	Snippet	Context
LOW	Src/Zle/zle_move.c	82	* Same principle when moving right. We need to check if	COMMENT