Painless E2E Automation for Mobile and Web
This report summarizes scanner evidence for mobile-dev-inc/Maestro, a Kotlin project with 16,274 GitHub stars. SynthScan examined 104,728 lines of code across 1386 source files, recording 86 pattern matches distributed across 10 syntactic categories. The legacy adjusted pattern signal is 1.9 (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.
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.
Can maintainers explain intent, assumptions, and trade-offs? 53 finding(s).
Are imports declared and package/API names verified? 16 finding(s).
Are wrappers, guards, and repeated structures necessary? 17 finding(s).
Which changes need focused human review? 86 finding(s).
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.
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.
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.
The scanner identified 86 distinct pattern matches across 10 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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL | …li/src/test/kotlin/maestro/cli/db/KeyValueStoreTest.kt | 133 | val classes = Path.of(LockProbe::class.java.protectionDomain.codeSource.location.toURI()).toString() | CODE |
| CRITICAL | …est/kotlin/maestro/cli/report/TestDebugReporterTest.kt | 35 | Files.setLastModifiedTime(oldDir, java.nio.file.attribute.FileTime.fromMillis(System.currentTimeMillis() - 1000 | CODE |
| CRITICAL | …in/java/maestro/cli/analytics/AnalyticsStateManager.kt | 255 | return java.time.temporal.ChronoUnit.DAYS.between(now, targetDate).toInt() | CODE |
| CRITICAL | …dels/src/test/kotlin/maestro/orchestra/util/EnvTest.kt | 152 | val error = org.junit.jupiter.api.Assertions.assertThrows(maestro.orchestra.util.Env.EnvVariableMissingValueErro | CODE |
| CRITICAL | …dels/src/test/kotlin/maestro/orchestra/util/EnvTest.kt | 164 | val error = org.junit.jupiter.api.Assertions.assertThrows(maestro.orchestra.util.Env.EnvVariableMissingValueErro | CODE |
| CRITICAL | …dels/src/test/kotlin/maestro/orchestra/util/EnvTest.kt | 179 | val error = org.junit.jupiter.api.Assertions.assertThrows(maestro.orchestra.util.Env.EnvVariableMissingValueErro | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …st/java/maestro/android/AndroidDeviceConnectionTest.kt | 60 | // ── Fake dadb: each method delegates to a lambda the test sets ─────────────── | COMMENT |
| MEDIUM | …st/java/maestro/android/AndroidDeviceConnectionTest.kt | 88 | // ── install: operation outcome is returned, transport death throws ────────── | COMMENT |
| MEDIUM | …st/java/maestro/android/AndroidDeviceConnectionTest.kt | 145 | // ── uninstall ─────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …st/java/maestro/android/AndroidDeviceConnectionTest.kt | 169 | // ── pull (both overloads) ───────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …st/java/maestro/android/AndroidDeviceConnectionTest.kt | 197 | // ── push (now honors its SyncResult too) ────────────────────────────────────── | COMMENT |
| MEDIUM | …st/java/maestro/android/AndroidDeviceConnectionTest.kt | 212 | // ── shell: exit code rides home; only transport throws ──────────────────────── | COMMENT |
| MEDIUM | …st/java/maestro/android/AndroidDeviceConnectionTest.kt | 420 | // ── gRPC plane: execute / stream ────────────────────────────────────────────── | COMMENT |
| MEDIUM | …c/main/java/maestro/android/AndroidDeviceConnection.kt | 112 | // ── gRPC plane ────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …c/main/java/maestro/android/AndroidDeviceConnection.kt | 144 | // ── dadb plane ────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …c/main/java/maestro/android/AndroidDeviceConnection.kt | 302 | // ── failure classification ──────────────────────────────────────────────── | COMMENT |
| MEDIUM | …c/main/java/maestro/android/AndroidDeviceConnection.kt | 376 | // ── the only Dadb.create / discover / list in the codebase ────────────── | COMMENT |
| MEDIUM | …n/java/maestro/android/AndroidDeviceConnectionModel.kt | 35 | // ────────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …n/java/maestro/android/AndroidDeviceConnectionModel.kt | 41 | // ────────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …n/java/maestro/android/AndroidDeviceConnectionModel.kt | 82 | // ────────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …n/java/maestro/android/AndroidDeviceConnectionModel.kt | 87 | // ────────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …n/java/maestro/android/AndroidDeviceConnectionModel.kt | 106 | // ────────────────────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | …n/java/maestro/android/AndroidDeviceConnectionModel.kt | 113 | // ────────────────────────────────────────────────────────────────────────────── | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | detekt.yml | 21 | # - 'PackageCountProcessor' | COMMENT |
| LOW | …test/src/test/kotlin/maestro/test/GraalJsEngineTest.kt | 101 | COMMENT | |
| LOW | .github/workflows/build-demo-app.yml | 1 | name: Build demo_app | COMMENT |
| LOW | .github/scripts/setup_android_device.sh | 1 | #!/bin/bash | COMMENT |
| LOW | .github/scripts/setup_android_device.sh | 41 | COMMENT | |
| LOW | maestro-ios-driver/src/main/resources/screenrecord.sh | 1 | # The `simctl recordVideo` command requires a SIGINT to be sent to stop the recording. | COMMENT |
| LOW | maestro-cli/src/test/mcp/inspect-screen-evals.yaml | 21 | criteria: > | COMMENT |
| LOW | maestro-cli/src/test/mcp/inspect-screen-evals.yaml | 41 | # criteria: > | COMMENT |
| LOW | maestro-cli/src/test/mcp/inspect-screen-evals.yaml | 61 | # The assistant correctly identifies exactly 8 clickable elements: 7 buttons in a column, and a final button in | COMMENT |
| LOW | maestro-cli/src/test/mcp/inspect-screen-evals.yaml | 81 | COMMENT | |
| LOW | maestro-cli/src/test/mcp/inspect-screen-evals.yaml | 101 | # I want to get a quick overview of all interactive elements on the screen for automated testing. | COMMENT |
| LOW | maestro-cli/src/test/mcp/inspect-screen-evals.yaml | 121 | # required: | COMMENT |
| LOW | maestro-cli/src/main/java/maestro/cli/App.kt | 121 | fun main(args: Array<String>) { | COMMENT |
| LOW | e2e/workspaces.txt | 1 | # The workspaces the e2e suite knows about, and what each one supports. | COMMENT |
| LOW | e2e/workspaces/web/flutter_semantics_identifier.yaml | 1 | # Flutter web id selector regression. The data: URL builds an element that | COMMENT |
| LOW | e2e/demo_app/analysis_options.yaml | 1 | # This file configures the analyzer, which statically analyzes Dart code to | COMMENT |
| LOW | e2e/demo_app/analysis_options.yaml | 21 | # `// ignore_for_file: name_of_lint` syntax on the line or in the file | COMMENT |
| LOW | …estro/android_device_configuration/enable_sensors.yaml | 1 | # Verifies all device sensors are available | COMMENT |
| LOW | e2e/demo_app/.maestro/commands/setOrientation.yaml | 1 | appId: com.example.example | COMMENT |
| LOW | e2e/demo_app/lib/carousel_screen.dart | 1 | import 'package:flutter/material.dart'; | COMMENT |
| LOW | e2e/alert-repro-swiftui/verify_preflight_suppressed.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | …ert-repro-swiftui/flows/ui_interruption_preflight.yaml | 1 | ## Regression target for the iOS XCTest UI-interruption preflight hang. | COMMENT |
| LOW | …ver-iosTests/maestro-driver-iosTests-Bridging-Header.h | 1 | // | COMMENT |
| LOW | …UITests/PrivateHeaders/XCTest/XCTRunnerDaemonSession.h | 1 | // | COMMENT |
| LOW | …driver-iosUITests/PrivateHeaders/XCTest/XCTestDriver.h | 1 | // | COMMENT |
| LOW | …Categories/maestro-driver-iosUITests-Bridging-Header.h | 1 | // | COMMENT |
| LOW | …verLib/Sources/MaestroDriverLib/MaestroDriverLib.swift | 1 | // MaestroDriverLib | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .claude/skills/release/SKILL.md | 44 | ## Step 0: say what will happen, then check the ground | COMMENT |
| LOW | .claude/skills/release/SKILL.md | 95 | ## Step 1: propose the version, draft the changelog (Checkpoint 1) | COMMENT |
| LOW | .claude/skills/release/SKILL.md | 142 | ## Step 2: draft everything, land nothing | COMMENT |
| LOW | .claude/skills/release/SKILL.md | 200 | ## Step 3: merge and tag (unattended) | COMMENT |
| LOW | .claude/skills/release/SKILL.md | 232 | ## Step 4: publish the CLI (unattended) | COMMENT |
| LOW | .claude/skills/release/SKILL.md | 252 | ## Step 5: verify | COMMENT |
| LOW | .claude/skills/release/SKILL.md | 267 | ## Step 6: hand-off | COMMENT |
| LOW | .claude/skills/bump-android-version/SKILL.md | 64 | ## Step 3: push draft PR + dispatch | COMMENT |
| LOW | .claude/skills/bump-android-version/SKILL.md | 82 | ## Step 4: watch the test-android job | COMMENT |
| LOW | .claude/skills/bump-android-version/SKILL.md | 96 | ## Step 5: diagnose (delegated to subagent) | COMMENT |
| LOW⚡ | …ro-cli/src/test/mcp/setup/download-and-install-apps.sh | 33 | # Step 1: Download apps using e2e infrastructure | COMMENT |
| LOW⚡ | …ro-cli/src/test/mcp/setup/download-and-install-apps.sh | 38 | # Step 2: Install apps for the specified platform | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | maestro-cli/src/test/mcp/run_mcp_tool_tests.sh | 21 | # Check if Maestro CLI is built | COMMENT |
| LOW | maestro-cli/src/test/mcp/run_mcp_evals.sh | 23 | # Check if Maestro CLI is built | COMMENT |
| LOW | maestro-cli/src/test/mcp/setup/setup_and_run_eval.sh | 51 | # Check if Maestro CLI is built | COMMENT |
| LOW | maestro-cli/src/test/mcp/setup/setup_and_run_eval.sh | 102 | # Check if file exists, try relative to evals/ if not absolute | COMMENT |
| LOW⚡ | …ro-cli/src/test/mcp/setup/download-and-install-apps.sh | 25 | # Check if we can find the e2e directory | COMMENT |
| LOW | …stro-cli/src/test/mcp/setup/check-maestro-cli-built.sh | 4 | # Check if Maestro CLI is built for MCP testing | COMMENT |
| LOW | …stro-cli/src/test/mcp/setup/check-maestro-cli-built.sh | 15 | # Check if Maestro CLI is built | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | CHANGELOG.md | 542 | - Fix: Warnings generated by AI-powered commands aren't formatted nicely ([#2043](https://github.com/mobile-dev-inc/maes | CODE |
| HIGH | CHANGELOG.md | 546 | - Fix: display warnings generated by AI-powered commands in CLI output when `optional: true` ([#2026](https://github.com | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …tro/device/serialization/DeviceSpecSparseSerializer.kt | 93 | String::class -> "placeholder" | CODE |
| LOW | …o-test/src/test/kotlin/maestro/test/IntegrationTest.kt | 422 | driver.assertHasEvent(Event.InputText("user@example.com")) | CODE |
| LOW | maestro-cli/mcp-viewer/src/demo.tsx | 34 | { commandId: "8", yaml: 'inputText: "user@example.com"', depth: 0, status: "completed" }, | CODE |
| LOW | maestro-cli/mcp-viewer/src/demo.tsx | 39 | { commandId: "13", yaml: 'inputText: "user@example.com"', depth: 0, status: "completed" }, | CODE |
| LOW | e2e/demo_app/.maestro/issues/issue1777.yaml | 6 | - inputText: "Lorem ipsum dolor sit amet" | CODE |
| LOW | e2e/demo_app/.maestro/issues/issue1777.yaml | 6 | - inputText: "Lorem ipsum dolor sit amet" | CODE |
| LOW | e2e/demo_app/lib/defects_screen.dart | 73 | 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna | CODE |
| LOW | e2e/demo_app/lib/defects_screen.dart | 73 | 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna | CODE |
| LOW | …erLib/Tests/MaestroDriverLibTests/AXElementTests.swift | 31 | placeholderValue: "placeholder", | CODE |
| LOW | …erLib/Tests/MaestroDriverLibTests/AXElementTests.swift | 48 | XCTAssertEqual(element.placeholderValue, "placeholder") | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | .github/scripts/boot_simulator.sh | 7 | # Create a unique identifier for the new simulator to avoid naming conflicts | COMMENT |
| MEDIUM | .github/scripts/boot_simulator.sh | 12 | # Create the simulator | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | …ro-cli/src/test/mcp/setup/download-and-install-apps.sh | 33 | # Step 1: Download apps using e2e infrastructure | COMMENT |
| LOW⚡ | …ro-cli/src/test/mcp/setup/download-and-install-apps.sh | 38 | # Step 2: Install apps for the specified platform | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | README.md | 28 | - [Maestro MCP – Agentic UI Testing](#maestro-mcp--agentic-ui-testing) | CODE |