AI Slop Code RIsk Monitor

YTLitePlus/YTLitePlus

⚠️ DEPRECATED — DEAD for now as YTPlus is now paid.

14.0 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for YTLitePlus/YTLitePlus, a Logos project with 3,619 GitHub stars. SynthScan examined 1,110 lines of code across 12 source files, recording 11 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 14.0 (Moderate 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.

14.0
Adjusted Signal
14.0
Raw Pattern Score
100%
Time Factor
2026-09-04
Last Push
3.6K
Stars
Logos
Language
1.1K
Lines of Code
12
Files
11
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 43.0/100 · MEDIUM

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

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

PR Review Velocity Impact 49.1/100 · MEDIUM

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

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

Redundant / Tautological Comments3 hits · 4 pts
SeverityFileLineSnippetContext
LOWbuild.sh6# Check if PATHTOYT is emptyCOMMENT
LOWbuild.sh11 # Check if there are two or more ipa/app filesCOMMENT
LOWSource/get_keys.py46 # Check if adding the next key would exceed the line length limitCOMMENT
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWYTLitePlus.h1#import <UIKit/UIKit.h>COMMENT
LOWYTLitePlus.h21#import "Tweaks/YouTubeHeader/YTIGuideResponse.h"COMMENT
LOWYTLitePlus.h41#import "Tweaks/YouTubeHeader/YTInlinePlayerBarContainerView.h"COMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMSource/get_keys.py14 # Define the regex pattern to match the strings that resemble the given examplesCOMMENT
Excessive Try-Catch Wrapping2 hits · 3 pts
SeverityFileLineSnippetContext
LOWSource/get_keys.py25 except Exception as e:CODE
MEDIUMSource/get_keys.py26 print(f"Error reading {file_path}: {e}")CODE
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWSource/get_keys.py59CODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/buildapp.yml152 def remove_uisupporteddevices(filepath):CODE