AI Slop Code Risk Monitor

appium/appium

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

Cross-platform automation framework for all kinds of apps, built on top of the W3C WebDriver protocol

0.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for appium/appium, a TypeScript project with 22,167 GitHub stars. SynthScan examined 142,490 lines of code across 850 source files, recording 37 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 0.3 (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.3
Adjusted Signal
0.3
Raw Pattern Score
100%
Time Factor
2026-10-31
Last Push
22.2K
Stars
TypeScript
Language
142.5K
Lines of Code
850
Files
37
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 1.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.9/100 · LOW

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

PR Review Velocity Impact 1.5/100 · LOW

Which changes need focused human review? 37 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 1MEDIUM 0LOW 36

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 37 distinct pattern matches across 5 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.

Hyper-Verbose Identifiers26 hits · 26 pts
SeverityFileLineSnippetContext
LOWpackages/fake-driver/lib/commands/find.ts11export function getExistingElementForNode(this: FakeDriver, node: FakeElement): string | null {CODE
LOWpackages/base-driver/lib/express/websocket.ts62export async function removeAllWebSocketHandlers(this: AppiumServer): Promise<boolean> {CODE
LOWpackages/base-driver/lib/express/middleware.ts44export function allowCrossDomainAsyncExecute(basePath: string): RequestHandler {CODE
LOWpackages/base-driver/lib/express/middleware.ts45 function allowCrossDomainAsyncExecuteHandler(req: Request, res: Response, next: NextFunction): void {CODE
LOWpackages/base-driver/lib/express/middleware.ts114export function tryHandleWebSocketUpgrade({CODE
LOWpackages/base-driver/lib/protocol/errors.ts943function generateBadParametersMessage(paramRequirements: ParameterRequirements, paramNames: string[]): string {CODE
LOWpackages/base-driver/lib/protocol/errors.ts1073export function errorFromMJSONWPStatusCode(code: number, value: string | {message: string} = ''): ProtocolError {CODE
LOWpackages/base-driver/lib/protocol/protocol.ts228export function validateExecuteMethodParams(params: any[], paramSpec?: PayloadParams): any[] {CODE
LOWpackages/base-driver/lib/protocol/protocol.ts363function hasMultipleRequiredParamSets(CODE
LOWpackages/base-driver/lib/basedriver/helpers.ts500export function filenameFromContentDisposition(header: string): string | undefined {CODE
LOW…e-driver/lib/basedriver/commands/bidi-subscriptions.ts21export function refreshEventSubscriptions(driver: BidiSubscriptionDriver): void {CODE
LOWpackages/base-driver/lib/helpers/levenshtein-match.ts21export function rankLevenshteinCandidates(CODE
LOWpackages/base-driver/lib/helpers/levenshtein-match.ts61export function sortByLevenshteinDistance(target: string, candidates: readonly string[]): string[] {CODE
LOWpackages/support/test/unit/logger/helpers.ts37export function assertOutputDoesntContain(writers: ReturnType<typeof setupWriters>, output: string) {CODE
LOWpackages/support/lib/zip.ts390async function assertFileDestinationWithinRoot(CODE
LOWpackages/support/lib/zip.ts700async function processYauzlEntriesSequentially(CODE
LOWpackages/support/lib/env.ts36export const findAppiumDependencyPackage = memoize(async function findAppiumDependencyPackage(CODE
LOWpackages/support/lib/env.ts92function isMissingPackageJsonError(err: unknown): boolean {CODE
LOWpackages/appium/test/e2e/e2e-helpers.ts164export async function readAppiumArgErrorFixture(name: string): Promise<string> {CODE
LOWpackages/appium/test/e2e/e2e-helpers.ts170export function formatAppiumArgErrorOutput(stderr: string): string {CODE
LOWpackages/appium/lib/inspector-commands.ts99function methodMapToRestCommandsInfo(mm: MethodMap<any>): Record<string, RestMethodsToCommandsMap> {CODE
LOWpackages/appium/lib/inspector-commands.ts116function executeMethodMapToCommandsInfo(emm: ExecuteMethodMap<any>): RestMethodsToCommandsMap {CODE
LOWpackages/appium/lib/bootstrap/main-helpers.ts55export function determineAppiumHomeSource(appiumHomeFromArgs?: string | null): string {CODE
LOWpackages/appium/lib/bootstrap/main-helpers.ts214function logDefaultCapabilitiesWarning(caps: ParsedArgs<CliCommandServer>['defaultCapabilities']): void {CODE
LOWpackages/appium/lib/cli/extension-command.ts1320async function getRemoteExtensionLatestStableMajors(pkgName: string): Promise<string[]> {CODE
LOWpackages/appium/lib/cli/extension-command.ts1341async function getRemoteExtensionVersionReq(pkgName: string, pkgVer?: string): Promise<string | null> {CODE
Fake / Example Data6 hits · 6 pts
SeverityFileLineSnippetContext
LOWpackages/fake-plugin/lib/plugin.ts21 '/session/:sessionId/fake_data': {CODE
LOWpackages/appium/test/e2e/plugin.e2e.spec.ts171 await axios.post(`${testServerBaseSessionUrl}/${sessionId}/fake_data`, {CODE
LOWpackages/appium/test/e2e/plugin.e2e.spec.ts174 assert.deepStrictEqual((await axios.get(`${testServerBaseSessionUrl}/${sessionId}/fake_data`)).data.value, {CODE
LOWpackages/appium/docs/ja/developing/build-plugins.md345 '/session/:sessionId/fake_data': {CODE
LOWpackages/appium/docs/zh/developing/build-plugins.md256 '/session/:sessionId/fake_data': {CODE
LOWpackages/appium/docs/en/developing/build-plugins.md341 '/session/:sessionId/fake_data': {CODE
Cross-Language Confusion (JS/TS)1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHpackages/appium/lib/extension/extension-config.ts260 print(_activeNames?: ExtName<ExtType>[]): void {CODE
Over-Commented Block3 hits · 3 pts
SeverityFileLineSnippetContext
LOWpackages/images-plugin/lib/types.ts21 // if the image returned by getScreenshot differs in size or aspect ratioCOMMENT
LOWpackages/images-plugin/lib/types.ts41 // e.g. If a user has an image of 270 x 32 pixels which was originally 1080 x 126 pixels,COMMENT
LOWpackages/appium/lib/appium.ts681COMMENT
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/workflows/build.yml70 # Check if package.json has test:e2e script and it's not a no-opCOMMENT