Repository Analysis

RROrg/rr

Redpill Recovery (arpl-i18n)

2.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of RROrg/rr, a Shell project with 8,450 GitHub stars. SynthScan v2.0 examined 15,413 lines of code across 38 source files, recording 33 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 2.4 places this repository in the Likely human-written 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).

2.4
Adjusted Score
2.4
Raw Score
100%
Time Factor
2026-07-14
Last Push
8.4K
Stars
Shell
Language
15.4K
Lines of Code
38
Files
33
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 0LOW 33

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 33 distinct pattern matches across 6 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.

Redundant / Tautological Comments10 hits · 14 pts
SeverityFileLineSnippetContext
LOWfiles/initrd/opt/rr/ramdisk-patch.sh59# Check if DSM buildnumber changedCOMMENT
LOWfiles/initrd/opt/rr/menu.sh694 arrayExistItem "${ADDON}" "${!ADDONS[@]}" && continue # Check if addon has already been addedCODE
LOWfiles/initrd/opt/rr/init.sh183 # Check if DSM buildnumber changedCOMMENT
LOWfiles/initrd/opt/rr/boot.sh23# Check if machine has EFICOMMENT
LOWfiles/initrd/opt/rr/boot.sh66# Check if DSM zImage changed, patch it if necessaryCOMMENT
LOWfiles/initrd/opt/rr/boot.sh316# Check if user wants to modify at this stageCOMMENT
LOWfiles/initrd/opt/rr/include/functions.sh36# Check if loader is fully configuredCOMMENT
LOWfiles/initrd/opt/rr/include/functions.sh47# Check if DSM upgrade happenedCOMMENT
LOWfiles/initrd/opt/rr/include/functions.sh90# Check if an item exists in an arrayCOMMENT
LOWfiles/initrd/opt/rr/include/addons.sh54# Check if addon existCOMMENT
Excessive Try-Catch Wrapping10 hits · 10 pts
SeverityFileLineSnippetContext
LOWscripts/func.py65 except Exception as e:CODE
LOWscripts/func.py173 except Exception as e:CODE
LOWscripts/func.py211 except Exception as e:CODE
LOWscripts/func.py266 except Exception as e:CODE
LOWscripts/func.py304 except Exception as e:CODE
LOW.github/workflows/issues.yml66 except Exception:CODE
LOWfiles/initrd/opt/rr/include/functions.py106 except Exception as e:CODE
LOWfiles/initrd/opt/rr/include/functions.py152 except Exception as e:CODE
LOWfiles/initrd/opt/rr/include/functions.py198 except Exception as e:CODE
LOWfiles/initrd/opt/rr/include/functions.py297 except Exception as e:CODE
Over-Commented Block7 hits · 7 pts
SeverityFileLineSnippetContext
LOWscripts/func.sh1#!/usr/bin/env bashCOMMENT
LOWfiles/initrd/opt/rr/menu.sh3281 writeConfigKey "bootipwait" "${BOOTIPWAIT}" "${USER_CONFIG_FILE}"COMMENT
LOWfiles/initrd/opt/rr/include/functions.py1# -*- coding: utf-8 -*-COMMENT
LOWfiles/initrd/opt/rr/include/modules.sh1#!/usr/bin/env bashCOMMENT
LOWfiles/initrd/opt/rr/include/configFile.sh1#!/usr/bin/env bashCOMMENT
LOWfiles/initrd/opt/rr/include/addons.sh1#!/usr/bin/env bashCOMMENT
LOWfiles/mnt/p1/boot/grub/gfxblacklist.txt1# GRUB gfxpayload blacklist. The format is a sequence of lines of theCOMMENT
Deep Nesting4 hits · 4 pts
SeverityFileLineSnippetContext
LOWscripts/func.py103CODE
LOWscripts/func.py399CODE
LOWfiles/initrd/opt/rr/include/functions.py54CODE
LOWfiles/initrd/opt/rr/include/functions.py209CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWscripts/func.py9CODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOWfiles/initrd/opt/rr/include/functions.py27def mutually_exclusive_options(ctx, param, value):CODE