Let's upgrade cheap off-the-shelf robotic mowers to modern, smart RTK GPS based lawn mowing robots!
This report presents the forensic synthetic code analysis of ClemensElflein/OpenMower, a Shell project with 6,667 GitHub stars. SynthScan v2.0 examined 4,209 lines of code across 30 source files, recording 45 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 11.5 places this repository in the Low AI signal band.
The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).
Longitudinal tracking requires multiple scan runs. Once this repository is re-scanned after new commits land, this chart will visualise how the synthetic code signal evolves over time — enabling you to detect whether AI authorship is growing, stabilising, or being actively corrected by human engineers.
Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.
This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.
The scanner identified 45 distinct pattern matches across 4 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .github/workflows/os-build.yaml | 141 | # content-hash-keyed cache below: they hold Buildroot's per-package | COMMENT |
| LOW | .github/workflows/os-build.yaml | 161 | # every single run, and force-wipes .stamp_configured/.stamp_built | COMMENT |
| LOW | .github/workflows/os-build.yaml | 201 | key: os-build-output-${{ steps.buildroot-rev.outputs.sha }}-${{ hashFiles('os/external/configs/openmower_defco | COMMENT |
| LOW | .github/workflows/os-build.yaml | 281 | uses: actions/cache/save@v4 | COMMENT |
| LOW | .github/workflows/os-build.yaml | 301 | # from a real failure). Skip the attempt entirely instead. | COMMENT |
| LOW | .github/workflows/os-build.yaml | 321 | with: | COMMENT |
| LOW | os/build.sh | 1 | #!/usr/bin/env bash | COMMENT |
| LOW | os/build.sh | 101 | else | COMMENT |
| LOW | os/build.sh | 121 | # delete every package's .stamp_target_installed/.stamp_staging_installed | COMMENT |
| LOW | os/build.sh | 161 | # same staleness reasoning applies to each; the satellites are cheap | COMMENT |
| LOW | os/build.sh | 181 | # reconfigured: same bug class as the target/staging wipe above, one stage | COMMENT |
| LOW | os/build.sh | 221 | "$HERE/keys-gen-dev.sh" | COMMENT |
| LOW | os/build.sh | 241 | # build just docker-loads and vendors that, | COMMENT |
| LOW | os/build.sh | 321 | echo -n "$OMR_KEY" > "$OMR_CACHE/.br-content-hash" | COMMENT |
| LOW | os/build.sh | 421 | menuconfig | menuconfig-migration | menuconfig-kernel-cm4 | menuconfig-kernel-cm5) | 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 | # ever recreates it. A symlink placed here (or in post-fakeroot.sh, or via | COMMENT |
| LOW | os/external/board/openmower/post-build.sh | 241 | # Dockge, ttyd): /opt/stacks and /opt/dockge are the paths Dockge's own | COMMENT |
| LOW | os/external/board/openmower/post-image.sh | 1 | #!/bin/bash | COMMENT |
| LOW | os/external/board/openmower/post-image.sh | 21 | # on the specific pinned firmware blob version (rpi-firmware.mk) actually | COMMENT |
| LOW | os/external/board/openmower/post-fakeroot.sh | 1 | #!/bin/sh | COMMENT |
| LOW | os/external/board/openmower/device_table.txt | 1 | # Applied by Buildroot under fakeroot when creating the target filesystem. | 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 | 433 | # just set there instead. Harmless no-op diff if nothing changed | COMMENT |