Repository Analysis

ophub/amlogic-s9xxx-openwrt

Supports running OpenWrt on Amlogic, Allwinner, and Rockchip devices. Support a311d, s922x, s905x3, s905x2, s912, s905d, s905x, s905w, s905, s905l, rk3588, rk3568, rk3399, rk3328, h6, etc.

25.8 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of ophub/amlogic-s9xxx-openwrt, a Shell project with 2,928 GitHub stars. SynthScan v2.0 examined 5,771 lines of code across 26 source files, recording 56 pattern matches distributed across 4 syntactic categories. The overall adjusted score of 25.8 places this repository in the Moderate 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).

25.8
Adjusted Score
25.8
Raw Score
100%
Time Factor
2026-07-14
Last Push
2.9K
Stars
Shell
Language
5.8K
Lines of Code
26
Files
56
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 38LOW 18

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 56 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.

Decorative Section Separators32 hits · 102 pts
SeverityFileLineSnippetContext
MEDIUMconfig/docker/make_docker_image.sh2#================================================================================================COMMENT
MEDIUMconfig/docker/make_docker_image.sh50#================================================================================================COMMENT
MEDIUMconfig/lede_master/diy-part2.sh2#=======================================================================================================================COMMENT
MEDIUMconfig/lede_master/diy-part2.sh7#=======================================================================================================================COMMENT
MEDIUMconfig/lede_master/diy-part1.sh2#=======================================================================================================================COMMENT
MEDIUMconfig/lede_master/diy-part1.sh7#=======================================================================================================================COMMENT
MEDIUMconfig/imagebuilder/imagebuilder.sh2#================================================================================================COMMENT
MEDIUMconfig/imagebuilder/imagebuilder.sh57#================================================================================================COMMENT
MEDIUMconfig/openwrt_main/diy-part2.sh2#=======================================================================================================================COMMENT
MEDIUMconfig/openwrt_main/diy-part2.sh7#=======================================================================================================================COMMENT
MEDIUMconfig/openwrt_main/diy-part1.sh2#=======================================================================================================================COMMENT
MEDIUMconfig/openwrt_main/diy-part1.sh7#=======================================================================================================================COMMENT
MEDIUMconfig/immortalwrt_master/diy-part2.sh2#=======================================================================================================================COMMENT
MEDIUMconfig/immortalwrt_master/diy-part2.sh7#=======================================================================================================================COMMENT
MEDIUMconfig/immortalwrt_master/diy-part1.sh2#=======================================================================================================================COMMENT
MEDIUMconfig/immortalwrt_master/diy-part1.sh7#=======================================================================================================================COMMENT
MEDIUM…files/common-files/etc/custom_service/start_service.sh2#========================================================================================COMMENT
MEDIUM…files/common-files/etc/custom_service/start_service.sh17#========================================================================================COMMENT
MEDIUM…ithub/workflows/build-openwrt-using-releases-files.yml1#=====================================================================================COMMENT
MEDIUM…ithub/workflows/build-openwrt-using-releases-files.yml4#=====================================================================================COMMENT
MEDIUM…thub/workflows/build-openwrt-using-unifreq-scripts.yml1#==========================================================================COMMENT
MEDIUM…thub/workflows/build-openwrt-using-unifreq-scripts.yml5#==========================================================================COMMENT
MEDIUM.github/workflows/compile-kernel.yml1#==========================================================================COMMENT
MEDIUM.github/workflows/compile-kernel.yml5#==========================================================================COMMENT
MEDIUM.github/workflows/delete-older-releases-workflows.yml1#==========================================================================COMMENT
MEDIUM.github/workflows/delete-older-releases-workflows.yml4#==========================================================================COMMENT
MEDIUM.github/workflows/build-openwrt-system-image.yml1#============================================================================================COMMENT
MEDIUM.github/workflows/build-openwrt-system-image.yml4#============================================================================================COMMENT
MEDIUM.github/workflows/build-openwrt-using-imagebuilder.yml1#=====================================================================================COMMENT
MEDIUM.github/workflows/build-openwrt-using-imagebuilder.yml7#=====================================================================================COMMENT
MEDIUM.github/workflows/build-openwer-docker-image.yml1#=====================================================================================COMMENT
MEDIUM.github/workflows/build-openwer-docker-image.yml5#=====================================================================================COMMENT
Self-Referential Comments6 hits · 27 pts
SeverityFileLineSnippetContext
MEDIUMconfig/docker/make_docker_image.sh4# This file is licensed under the terms of the GNU General PublicCOMMENT
MEDIUMconfig/docker/make_docker_image.sh8# This file is a part of the OpenWrt Docker Image BuilderCOMMENT
MEDIUMconfig/imagebuilder/imagebuilder.sh4# This file is licensed under the terms of the GNU General PublicCOMMENT
MEDIUMconfig/imagebuilder/imagebuilder.sh8# This file is a part of the OpenWrt Image Builder workflowCOMMENT
MEDIUM…files/common-files/etc/custom_service/start_service.sh4# This file is licensed under the terms of the GNU General PublicCOMMENT
MEDIUM…files/common-files/etc/custom_service/start_service.sh8# This file is a part of the make OpenWrt for Amlogic, Rockchip and AllwinnerCOMMENT
Over-Commented Block14 hits · 14 pts
SeverityFileLineSnippetContext
LOWconfig/docker/make_docker_image.sh1#!/bin/bashCOMMENT
LOWconfig/lede_master/diy-part2.sh1#!/bin/bashCOMMENT
LOWconfig/lede_master/diy-part2.sh41elseCOMMENT
LOWconfig/lede_master/diy-part1.sh1#!/bin/bashCOMMENT
LOWconfig/imagebuilder/imagebuilder.sh1#!/bin/bashCOMMENT
LOWconfig/imagebuilder/imagebuilder.sh21# Instructions: Download the official OpenWrt Image Builder,COMMENT
LOWconfig/openwrt_main/diy-part2.sh1#!/bin/bashCOMMENT
LOWconfig/openwrt_main/diy-part2.sh41 echo 'CONFIG_CCACHE_DIR=""' >>.configCOMMENT
LOWconfig/openwrt_main/diy-part1.sh1#!/bin/bashCOMMENT
LOWconfig/immortalwrt_master/diy-part2.sh1#!/bin/bashCOMMENT
LOWconfig/immortalwrt_master/diy-part2.sh41 echo 'CONFIG_CCACHE_DIR=""' >>.configCOMMENT
LOWconfig/immortalwrt_master/diy-part1.sh1#!/bin/bashCOMMENT
LOW…files/common-files/etc/custom_service/start_service.sh1#!/bin/bashCOMMENT
LOWdocuments/README.cn.md641如果你的现象如上所示,那么你需要在 TTL 上焊接一个电阻了: [X96 Max Plus's V4.0 主板示意图](https://user-images.githubusercontent.com/68696949/110910162COMMENT
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWconfig/docker/make_docker_image.sh79 # Check if docker command existsCOMMENT
LOWconfig/docker/make_docker_image.sh84 # Check if Docker daemon is runningCOMMENT
LOWconfig/imagebuilder/imagebuilder.sh245 # Check if the original archive existsCOMMENT
LOW…files/common-files/etc/custom_service/start_service.sh173 # Set MTU to 1500 for eth0 and br-lanCOMMENT