AI Slop Code Risk Monitor

smogon/pokemon-showdown

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

Pokémon battle simulator.

0.0 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for smogon/pokemon-showdown, a TypeScript project with 6,010 GitHub stars. SynthScan examined 829,082 lines of code across 1018 source files, recording 31 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 0.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.

0.0
Adjusted Signal
0.0
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
6.0K
Stars
TypeScript
Language
829.1K
Lines of Code
1.0K
Files
31
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.2/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 30 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 1 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 0.2/100 · LOW

Which changes need focused human review? 31 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 3LOW 28

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 31 distinct pattern matches across 9 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 Block14 hits · 14 pts
SeverityFileLineSnippetContext
LOWtest/sim/data.js441 formes[6] = formes[5] + 1 + 2 + 1 + 2 + 1 + 3 + 3 + 1 + 6 + 48;COMMENT
LOWconfig/formats.ts841 'Uber', 'AG', 'Arena Trap', 'Moody', 'Shadow Tag', 'King\'s Rock', 'Razor Fang', 'Baton Pass',COMMENT
LOWconfig/formats.ts3041 // The "???" type never gets STABCOMMENT
LOWserver/chat.ts1621COMMENT
LOWserver/rooms.ts2041 * NOT: PS server -> loginserverCOMMENT
LOWsim/state.ts21// the simulator only gives a position to active Pokemon, serializationCOMMENT
LOWsim/state.ts101 // serialized. See serializeSide below for an explanation about theCOMMENT
LOWsim/state.ts261 return obj.hasOwnProperty('hit') && (obj.hasOwnProperty('id') || obj.hasOwnProperty('move'));COMMENT
LOWsim/tools/exhaustive-runner.ts341 // Returns the next option in our set of unused options which were shuffledCOMMENT
LOWdata/mods/gen1/scripts.ts581COMMENT
LOWdata/text/ja/moves.ts1// Mechanics desc conventions (ja) — keep consistent with ja/abilities.ts and ja/items.ts:COMMENT
LOWdata/text/zh-cn/moves.ts1// Mechanics desc style (zh-cn): official game terminology, halfwidth numerals (1.5倍, 30%, 2~5次).COMMENT
LOWdata/text/zh-tw/moves.ts1// Mechanics desc style (zh-tw): official game terminology, halfwidth numerals (1.5倍, 30%, 2~5次).COMMENT
LOWdata/text/en-afd/default.ts1export const DefaultText: { [id: IDEntry]: DefaultText } = {COMMENT
TODO Padding5 hits · 7 pts
SeverityFileLineSnippetContext
LOWserver/ladders.ts478 if (formatTable.playerCount > 2) continue; // TODO: implementCODE
LOWserver/chat-plugins/battlesearch.ts286 // TODO: implement flag?COMMENT
LOWsim/battle-actions.ts352 // TODO: implement properlyCOMMENT
LOWdata/mods/linked/scripts.ts436 // TODO: implement properlyCOMMENT
LOWdata/mods/gen9ssb/scripts.ts1123 // TODO: implement properlyCOMMENT
Hyper-Verbose Identifiers6 hits · 6 pts
SeverityFileLineSnippetContext
LOWserver/chat-commands/admin.ts66function keysIncludingNonEnumerable(obj: object) {CODE
LOWserver/chat-plugins/datasearch.ts636function prepareDexsearchValidator(usedMod: string | undefined, rules: FormatData[], nationalSearch: boolean | null) {CODE
LOWserver/chat-plugins/calculator.ts51function parseMathematicalExpression(infix: string) {CODE
LOWserver/chat-plugins/randombattles/index.ts18function getHTMLCriteriaDescription(criteria: SetCriteria) {CODE
LOWserver/chat-plugins/trivia/trivia.ts175function getTriviaOrMastermindGame(room: Room | null) {CODE
LOWserver/tournaments/index.ts1095function createTournamentGenerator(CODE
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMtools/build-utils.js33 // fix this function to be more robust.COMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMserver/artemis/model.py1# This file handles the actual processing of messages,COMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMserver/chat-plugins/scavengers.ts2696 "<br />As a <strong>room owner (#)</strong>, you can also use the following scavengers commands:",CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/workflows/publish.yml22 # Check if the package.json version field has changed since the last pushCOMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWconfig/config-example.js243 to: 'admin@example.com',CODE
Overly Generic Function Names1 hit · 1 pts
SeverityFileLineSnippetContext
LOWserver/chat-plugins/randombattles/index.ts177function getData(species: string | Species, format: string | Format): AnyObject | null {CODE