AI Slop Code Risk Monitor

ish-app/ish

SlopCodeMonitor badge for ish-app/ish Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Linux shell for iOS

3.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for ish-app/ish, a C project with 20,657 GitHub stars. SynthScan examined 50,996 lines of code across 333 source files, recording 153 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 3.0 (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.0
Adjusted Signal
3.0
Raw Pattern Score
100%
Time Factor
2026-10-24
Last Push
20.7K
Stars
C
Language
51.0K
Lines of Code
333
Files
153
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 14.0/100 · LOW

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

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

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 153 distinct pattern matches across 2 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 Block152 hits · 152 pts
SeverityFileLineSnippetContext
LOWxX_main_Xx.h1#include <string.h>COMMENT
LOWdebug.h1#ifndef UTIL_DEBUG_HCOMMENT
LOWdebug.h21#define DEBUG_instr DEBUG_allCOMMENT
LOWdebug.h41#define TRACE_instr TRACE__NOPCOMMENT
LOWdebug.h61#define TRACE__NOP(msg, ...) if (log_override) { TRACE__(msg, ##__VA_ARGS__); }COMMENT
LOWdebug.h81#if defined(__i386__) || defined(__x86_64__)COMMENT
LOWmisc.h1#ifndef MISC_HCOMMENT
LOWmisc.h21#define _str(x) #xCOMMENT
LOWmisc.h41#define forceinline inline __attribute__((always_inline))COMMENT
LOWmisc.h61#if has_attribute(no_sanitize)COMMENT
LOWmisc.h121typedef dword_t time_t_;COMMENT
LOWemu/float80.c1#include <assert.h>COMMENT
LOWemu/mmu.h1#ifndef EMU_CPU_MEM_HCOMMENT
LOWemu/mmu.h41#endifCOMMENT
LOWemu/interrupt.h1// Intel standard interruptsCOMMENT
LOWemu/float80-test.c1#include <stdio.h>COMMENT
LOWemu/decode.h1#include "misc.h"COMMENT
LOWtools/undefined-flags.c1#include "emu/modrm.h"COMMENT
LOWtools/ptutil.c1#define _GNU_SOURCECOMMENT
LOWtools/vdso-transplant-main.c1// Run a process but replace the vdso with the one in the given file.COMMENT
LOWtools/ptraceomatic-config.h1#define VVAR_PAGES 4COMMENT
LOWtools/ptraceomatic.c1// Fun little utility that single-steps a program using ptrace andCOMMENT
LOWtools/ptraceomatic.c21#include "fs/fd.h"COMMENT
LOWtools/fakefs.c1#include <errno.h>COMMENT
LOWtools/vdso-transplant.c1// Uses ptrace to overwrite the vdso of a running process.COMMENT
LOWtools/unicornomatic.c1// Runs a program simultaneously in ish and unicorn, single steps, and assertsCOMMENT
LOWapp/LinuxTTY.c1//COMMENT
LOWapp/UpgradeRootViewController.m1//COMMENT
LOWapp/AppGroup.h1//COMMENT
LOWapp/LinuxInterop.h1//COMMENT
LOWapp/PasteboardDevice.m1#include <string.h>COMMENT
LOWapp/Roots.m1//COMMENT
LOWapp/AboutViewController.m1//COMMENT
LOWapp/AboutAppearanceViewController.m1//COMMENT
LOWapp/AccessibilityFixes.m1//COMMENT
LOWapp/Terminal.m1//COMMENT
LOWapp/LinuxPTY.c1//COMMENT
LOWapp/CurrentRoot.h21/// An integer representing the current major version of the apk repositories. An upgrade will be run if the number in /COMMENT
LOWapp/LocationDevice.m1//COMMENT
LOWapp/hook.h1//COMMENT
LOWapp/ExceptionExfiltrator.m1//COMMENT
LOWapp/iOSFS.m1//COMMENT
LOWapp/PasteboardDeviceLinux.c1//COMMENT
LOWapp/LinuxInterop.c1//COMMENT
LOWapp/AppGroup.m1//COMMENT
LOWapp/LinuxRoot.c1//COMMENT
LOWapp/Terminal.h1//COMMENT
LOWapp/AppDelegate.m1//COMMENT
LOWapp/AppDelegate.m21#import "NSObject+SaneKVO.h"COMMENT
LOWapp/RootsTableViewController.m1//COMMENT
LOWapp/TerminalView.m1//COMMENT
LOWapp/UserPreferences.m1//COMMENT
LOWapp/hook.c1//COMMENT
LOWapp/LocationDevice.h1//COMMENT
LOWapp/TerminalViewController.m1//COMMENT
LOWapp/CurrentRoot.m1//COMMENT
LOWapp/IOSCalls.m1//COMMENT
LOWapp/ExceptionExfiltrator.h1//COMMENT
LOWapp/ThemesViewController.m1//COMMENT
LOWapp/FileProvider/FileProviderExtension.m1//COMMENT
92 more matches not shown…
Self-Referential Comments1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMapp/CurrentRoot.m91 NSMutableData *repositoriesData = [@"# This file contains pinned repositories managed by iSH. If the /ish directCODE