AI Slop Code Risk Monitor

MorpheApp/morphe-manager

Name: MorpheApp/morphe-manager — Kotlin 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).

Morphe app patcher for Android

0.2 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for MorpheApp/morphe-manager, a Kotlin project with 9,774 GitHub stars. SynthScan examined 256,903 lines of code across 763 source files, recording 32 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 0.2 (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.2

Adjusted Signal

0.2

Raw Pattern Score

100%

Time Factor

2026-10-31

Last Push

9.8K

Stars

Kotlin

Language

256.9K

Lines of Code

763

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

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

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

PR Review Velocity Impact 1.0/100 · LOW

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

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 32 distinct pattern matches across 6 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.

Structural Annotation Overuse11 hits · 19 pts

Severity	File	Line	Snippet	Context
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	111	// Step 1: update smoothed positions	COMMENT
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	146	// Step 2: draw each solid	COMMENT
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	255	// Step 1 - rotate around X (nod), Y (yaw), then Z (roll), and perspective-project	COMMENT
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	271	// Step 2 - faces point their normals outward and the viewer looks along +z, so a face is	COMMENT
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	297	// Step 3 - fill, the side turned to the light reading brighter than the side turned away	COMMENT
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	309	// Step 4 - draw every edge exactly once with depth-based alpha.	COMMENT
LOW	.github/workflows/crowdin_pull.yml	47	# Step 1: Checkout Crowdin branch to run checks on it	COMMENT
LOW	.github/workflows/crowdin_pull.yml	58	# Step 2: Compile Android app to check string resources	COMMENT
LOW⚡	.github/workflows/crowdin_pull.yml	74	# Step 3: Checkout dev branch to prepare for merging	COMMENT
LOW⚡	.github/workflows/crowdin_pull.yml	82	# Step 4: Fetch the latest crowdin branch (already checked)	COMMENT
LOW⚡	.github/workflows/crowdin_pull.yml	86	# Step 5: Squash merge crowdin into dev	COMMENT

Decorative Section Separators6 hits · 18 pts

Severity	File	Line	Snippet	Context
MEDIUM	.github/scripts/send_fcm.py	37	# ── Read environment ───────────────────────────────────────────────────────────	COMMENT
MEDIUM	.github/scripts/send_fcm.py	81	# ── Parse Service Account ──────────────────────────────────────────────────────	COMMENT
MEDIUM	.github/scripts/send_fcm.py	95	# ── Build and sign JWT ─────────────────────────────────────────────────────────	COMMENT
MEDIUM	.github/scripts/send_fcm.py	128	# ── Exchange JWT for OAuth2 access token ──────────────────────────────────────	COMMENT
MEDIUM	.github/scripts/send_fcm.py	147	# ── Build FCM message payload ──────────────────────────────────────────────────	COMMENT
MEDIUM	.github/scripts/send_fcm.py	164	# ── Send FCM request ───────────────────────────────────────────────────────────	COMMENT

Verbosity Indicators7 hits · 13 pts

Severity	File	Line	Snippet	Context
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	111	// Step 1: update smoothed positions	COMMENT
LOW	…nager/ui/screen/shared/backgrounds/ShapesBackground.kt	146	// Step 2: draw each solid	COMMENT
LOW	.github/workflows/crowdin_pull.yml	47	# Step 1: Checkout Crowdin branch to run checks on it	COMMENT
LOW	.github/workflows/crowdin_pull.yml	58	# Step 2: Compile Android app to check string resources	COMMENT
LOW⚡	.github/workflows/crowdin_pull.yml	74	# Step 3: Checkout dev branch to prepare for merging	COMMENT
LOW⚡	.github/workflows/crowdin_pull.yml	82	# Step 4: Fetch the latest crowdin branch (already checked)	COMMENT
LOW⚡	.github/workflows/crowdin_pull.yml	86	# Step 5: Squash merge crowdin into dev	COMMENT

AI Slop Vocabulary3 hits · 9 pts

Severity	File	Line	Snippet	Context
MEDIUM	…manager/ui/screen/shared/backgrounds/AnimationSpecs.kt	60	// It is a whole number of the cycles backgrounds wrap their own motion at, so those stay seamless	COMMENT
MEDIUM	…manager/ui/screen/shared/backgrounds/SnowBackground.kt	188	// Calculate alpha with edge fade for seamless loop	COMMENT
MEDIUM	…er/ui/screen/shared/backgrounds/HalloweenBackground.kt	27	// Every motion repeats a whole number of times per cycle, so the wrap of the clock is seamless	COMMENT

Excessive Try-Catch Wrapping3 hits · 3 pts

Severity	File	Line	Snippet	Context
LOW	.github/scripts/send_fcm.py	117	except Exception as e:	CODE
LOW	.github/scripts/send_fcm.py	141	except Exception as e:	CODE
LOW	.github/scripts/send_fcm.py	189	except Exception:	CODE

Over-Commented Block2 hits · 2 pts

Severity	File	Line	Snippet	Context
LOW	…main/java/app/morphe/manager/ui/viewmodel/PatchFlow.kt	861	return	COMMENT
LOW	app/src/main/cpp/jvm_launcher.cpp	1	// Starts a HotSpot JVM inside the calling process and runs a main class in it.	COMMENT