Repository Analysis

justcallmekoko/ESP32Marauder

A suite of WiFi/Bluetooth offensive and defensive tools for the ESP32

8.4 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of justcallmekoko/ESP32Marauder, a C++ project with 11,561 GitHub stars. SynthScan v2.0 examined 45,703 lines of code across 107 source files, recording 443 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 8.4 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).

8.4
Adjusted Score
8.4
Raw Score
100%
Time Factor
2026-07-14
Last Push
11.6K
Stars
C++
Language
45.7K
Lines of Code
107
Files
443
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

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.

No multi-scan history yet — run the scanner again to build trend data.

Severity Breakdown

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.

CRITICAL 0HIGH 0MEDIUM 6LOW 437

Directory Score Breakdown

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.

Pattern Findings

The scanner identified 443 distinct pattern matches across 5 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.

Over-Commented Block430 hits · 362 pts
SeverityFileLineSnippetContext
LOWUser_Setup_dual_nrf24.h1// USER DEFINED SETTINGSCOMMENT
LOWUser_Setup_dual_nrf24.h21// Only define one driver, the other ones must be commented outCOMMENT
LOWUser_Setup_dual_nrf24.h41// #define TFT_SDA_READ // This option is for ESP32 ONLY, tested with ST7789 display onlyCOMMENT
LOWUser_Setup_dual_nrf24.h61COMMENT
LOWUser_Setup_dual_nrf24.h81COMMENT
LOWUser_Setup_dual_nrf24.h101//COMMENT
LOWUser_Setup_dual_nrf24.h121// The NodeMCU D0 pin can be used for RSTCOMMENT
LOWUser_Setup_dual_nrf24.h141//#define TFT_WR PIN_D2 // Write strobe for modified Raspberry Pi TFT onlyCOMMENT
LOWUser_Setup_dual_nrf24.h161COMMENT
LOWUser_Setup_dual_nrf24.h181#define TFT_RST -1 // Reset pin (could connect to NodeMCU RST, see next line)COMMENT
LOWUser_Setup_dual_nrf24.h201COMMENT
LOWUser_Setup_dual_nrf24.h221// The library supports 8 bit parallel TFTs with the ESP32, the pinCOMMENT
LOWUser_Setup_dual_nrf24.h241//#define TFT_D2 26 // Pins can be randomly assigned, this does not affectCOMMENT
LOWUser_Setup_dual_nrf24.h261#define LOAD_FONT2 // Font 2. Small 16 pixel high font, needs ~3534 bytes in FLASH, 96 charactersCOMMENT
LOWUser_Setup_dual_nrf24.h281// fast and the TFT driver will not keep up and display corruption appears.COMMENT
LOWUser_Setup_dual_nrf24.h301// If the VSPI port is in use and pins are not accessible (e.g. TTGO T-Beam)COMMENT
LOWUser_Setup_cyd_2usb.h1// USER DEFINED SETTINGSCOMMENT
LOWUser_Setup_cyd_2usb.h21// Only define one driver, the other ones must be commented outCOMMENT
LOWUser_Setup_cyd_2usb.h41// #define TFT_SDA_READ // This option is for ESP32 ONLY, tested with ST7789 display onlyCOMMENT
LOWUser_Setup_cyd_2usb.h61COMMENT
LOWUser_Setup_cyd_2usb.h81COMMENT
LOWUser_Setup_cyd_2usb.h101//COMMENT
LOWUser_Setup_cyd_2usb.h121// The NodeMCU D0 pin can be used for RSTCOMMENT
LOWUser_Setup_cyd_2usb.h141//#define TFT_WR PIN_D2 // Write strobe for modified Raspberry Pi TFT onlyCOMMENT
LOWUser_Setup_cyd_2usb.h161COMMENT
LOWUser_Setup_cyd_2usb.h181#define TFT_SCLK 14COMMENT
LOWUser_Setup_cyd_2usb.h201//#define TFT_RST -1 // Set TFT_RST to -1 if display RESET is connected to ESP32 board RSTCOMMENT
LOWUser_Setup_cyd_2usb.h221COMMENT
LOWUser_Setup_cyd_2usb.h241//#define TFT_D1 13 // so a single register write sets/clears all bits.COMMENT
LOWUser_Setup_cyd_2usb.h261#define LOAD_GLCD // Font 1. Original Adafruit 8 pixel font needs ~1820 bytes in FLASHCOMMENT
LOWUser_Setup_cyd_2usb.h281// Define the SPI clock frequency, this affects the graphics rendering speed. TooCOMMENT
LOWUser_Setup_cyd_2usb.h301// The ESP32 has 2 free SPI ports i.e. VSPI and HSPI, the VSPI is the default.COMMENT
LOWUser_Setup.h1// USER DEFINED SETTINGSCOMMENT
LOWUser_Setup.h21//#define ILI9163_DRIVER // Define additional parameters below for this displayCOMMENT
LOWUser_Setup.h41COMMENT
LOWUser_Setup.h61// e.g. colours wrong, mirror images, or tray pixels at the edges.COMMENT
LOWUser_Setup.h81// If a backlight control signal is available then define the TFT_BL pin in Section 2COMMENT
LOWUser_Setup.h101// Display SDI/MOSI to NodeMCU pin D7COMMENT
LOWUser_Setup.h121// If 5V is not available at a pin you can use 3.3V but backlight brightnessCOMMENT
LOWUser_Setup.h141COMMENT
LOWUser_Setup.h161#define TFT_MISO 19 // Matching T_DOCOMMENT
LOWUser_Setup.h181//#define TFT_RST 33 // Reset pin (could connect to Arduino RESET pin)COMMENT
LOWUser_Setup.h201//#define TFT_WR 4 // Write strobe control pin - must use a pin in the range 0-31COMMENT
LOWUser_Setup.h221// The ESP8366 and ESP32 have plenty of memory so commenting out fonts is notCOMMENT
LOWUser_Setup.h241// Section 4. Other optionsCOMMENT
LOWUser_Setup.h261#define SPI_READ_FREQUENCY 20000000COMMENT
LOWUser_Setup_marauder_m5stickcp2.h1// USER DEFINED SETTINGSCOMMENT
LOWUser_Setup_marauder_m5stickcp2.h21// Section 1. Call up the right driver file and any options for itCOMMENT
LOWUser_Setup_marauder_m5stickcp2.h41//#defined TFT_PARALLEL_16_BIT // **** 16 bit parallel ONLY for RP2040 processor ****COMMENT
LOWUser_Setup_marauder_m5stickcp2.h61//#define ST7796_DRIVERCOMMENT
LOWUser_Setup_marauder_m5stickcp2.h81// For M5Stack ESP32 module with integrated ILI9341 display ONLY, remove // in line belowCOMMENT
LOWUser_Setup_marauder_m5stickcp2.h101// Comment out ALL BUT ONE of these options for a ST7735 display driver, save thisCOMMENT
LOWUser_Setup_marauder_m5stickcp2.h121COMMENT
LOWUser_Setup_marauder_m5stickcp2.h141//COMMENT
LOWUser_Setup_marauder_m5stickcp2.h161// The NodeMCU D0 pin can be used for RSTCOMMENT
LOWUser_Setup_marauder_m5stickcp2.h181COMMENT
LOWUser_Setup_marauder_m5stickcp2.h201COMMENT
LOWUser_Setup_marauder_m5stickcp2.h221COMMENT
LOWUser_Setup_marauder_m5stickcp2.h241#define TFT_DC 14 // Data Command control pinCOMMENT
LOWUser_Setup_marauder_m5stickcp2.h261//#define TFT_RST 32 // Reset pin, toggles on startupCOMMENT
370 more matches not shown…
Excessive Try-Catch Wrapping6 hits · 9 pts
SeverityFileLineSnippetContext
LOWC5_Py_Flasher_for_mini_v3/c5_flasher.py160 except Exception as e:CODE
MEDIUMC5_Py_Flasher_for_mini_v3/c5_flasher.py12def ensure_package(pkg):CODE
LOWC5_Py_Flasher_for_adapter/c5_flasher.py160 except Exception as e:CODE
MEDIUMC5_Py_Flasher_for_adapter/c5_flasher.py12def ensure_package(pkg):CODE
LOWC5_Py_Flasher_for_v8/c5_flasher.py160 except Exception as e:CODE
MEDIUMC5_Py_Flasher_for_v8/c5_flasher.py12def ensure_package(pkg):CODE
Decorative Section Separators3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMesp32_marauder/WiFiScan.cpp6229 // ── RSN IE (Tag 48) — indicates WPA2/WPA3 ────────────────────COMMENT
MEDIUMesp32_marauder/WiFiScan.cpp6275 // ── WPA IE (Tag 221, OUI 00:50:F2:01) — indicates WPA1 ───────COMMENT
MEDIUMesp32_marauder/WiFiScan.cpp6316 // ── Security type decision tree (most specific first) ────────────COMMENT
Unused Imports3 hits · 3 pts
SeverityFileLineSnippetContext
LOWC5_Py_Flasher_for_mini_v3/c5_flasher.py6CODE
LOWC5_Py_Flasher_for_adapter/c5_flasher.py6CODE
LOWC5_Py_Flasher_for_v8/c5_flasher.py6CODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWesp32_marauder/EvilPortal.h75class CaptiveRequestHandler : public AsyncWebHandler {CODE