Let's upgrade cheap off-the-shelf robotic mowers to modern, smart RTK GPS based lawn mowing robots!
This report summarizes scanner evidence for ClemensElflein/OpenMower, a Shell project with 6,727 GitHub stars. SynthScan examined 4,171 lines of code across 29 source files, recording 43 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 11.1 (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.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 43 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 43 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 43 distinct pattern matches across 4 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 |
|---|---|---|---|---|
| LOW | .github/workflows/os-build.yaml | 1 | name: OS Build | COMMENT |
| LOW | .github/workflows/os-build.yaml | 81 | echo "event=${{ github.event.client_payload.event }}" >> "$GITHUB_OUTPUT" | COMMENT |
| LOW | .github/workflows/os-build.yaml | 161 | COMMENT | |
| LOW | .github/workflows/os-build.yaml | 181 | # needed the delete-step below to actually take effect before the | COMMENT |
| LOW | .github/workflows/os-build.yaml | 221 | # re-staged-instead-of-reconfigured bug this split exists to avoid -- | COMMENT |
| LOW | .github/workflows/os-build.yaml | 321 | # No delete-first step needed here, same reasoning as the kernel | COMMENT |
| LOW | .github/workflows/os-build.yaml | 341 | # content-hash key (no delete-first step, no restore-keys fallback, and | COMMENT |
| LOW | .github/workflows/os-build.yaml | 361 | # upload ~6GB of unchanged kernel build output just to re-produce the | COMMENT |
| LOW | os/build.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | os/build.sh | 101 | else | COMMENT |
| LOW | os/build.sh | 141 | # same staleness reasoning applies to each; the satellites are cheap | COMMENT |
| LOW | os/build.sh | 181 | fi | COMMENT |
| LOW | os/build.sh | 221 | ;; | COMMENT |
| LOW | os/build.sh | 261 | "$OMR_DIR" | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 1 | #!/bin/sh | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 21 | # `make image-migration` need re-running. | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 41 | # the migration boot never gets far enough to trigger its own | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 61 | # image (a GitHub Releases asset -- pick whichever version you | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 141 | # BACK UP YOUR MAP AND SETTINGS NOW if you haven't already. This tool makes | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 161 | # --- Stop the running stack, reclaim disk space ----------------------------- | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 201 | # --- Locate the boot (firmware) partition ---------------------------------- | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 281 | echo "$IMG_SHA256 $IMG_GZ" | sha256sum -c - >/dev/null \ | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 381 | # --- Stage the migration boot files onto the EXISTING boot partition ---------- | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 401 | log "writing migration boot files to $BOOT_MIGRATION_DIR..." | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 461 | # Everything from here on is unreachable when embedded in a real installer | COMMENT |
| LOW | os/external/board/openmower/genimage.cfg | 1 | # Disk layout. MBR; genimage puts partitions 4+ into an extended partition, | COMMENT |
| LOW | os/external/board/openmower/genimage.cfg | 61 | image = "boot-a.vfat" | COMMENT |
| LOW | os/external/board/openmower/post-build.sh | 41 | # sides -- otherwise the two release dirs collide and one board's modules | COMMENT |
| LOW | os/external/board/openmower/post-build.sh | 101 | # Overwrites whatever BR2_TARGET_GENERIC_ISSUE put here at | COMMENT |
| LOW | os/external/board/openmower/post-build.sh | 181 | # prompt/aliases that go with it. | COMMENT |
| LOW | os/external/board/openmower/post-build.sh | 201 | install -D -m 0644 "$OS_DIR/keys/dev-cert.pem" "$TARGET_DIR/etc/rauc/keyring.pem" | COMMENT |
| LOW | os/external/board/openmower/post-build.sh | 221 | # root-password baking (SET_ROOT_PASSWD, part of TARGET_FINALIZE_HOOKS) | COMMENT |
| LOW | os/external/board/openmower/post-build.sh | 241 | # real boot-partition config.txt (already installed by the rpi-firmware | COMMENT |
| LOW | os/external/board/openmower/post-image.sh | 1 | #!/bin/bash | COMMENT |
| LOW | os/external/board/openmower/post-image.sh | 21 | # depend on it. | COMMENT |
| LOW | os/external/board/openmower/post-fakeroot.sh | 1 | #!/bin/sh | COMMENT |
| LOW | …ard/openmower/rootfs-overlay/etc/openocd/xcore-cm4.cfg | 1 | # SPDX-License-Identifier: GPL-2.0-or-later | COMMENT |
| LOW | …ard/openmower/rootfs-overlay/etc/openocd/xcore-cm5.cfg | 1 | # SPDX-License-Identifier: GPL-2.0-or-later | COMMENT |
| LOW | os/external/board/openmower-cm4-migration/post-image.sh | 1 | #!/bin/bash | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | os/build.sh | 4 | # Usage: | COMMENT |
| LOW | os/scripts/migrate-to-openmower.sh | 57 | # Usage: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | os/scripts/migrate-to-openmower.sh | 5 | # This file is the HEADER of a self-extracting installer: `make image-migration` | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | os/build.sh | 368 | # just set there instead. Harmless no-op diff if nothing changed | COMMENT |