Repository Analysis

007revad/Synology_HDD_db

Add your HDD, SSD and NVMe drives to your Synology's compatible drive database and a lot more

17.5 Moderate AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of 007revad/Synology_HDD_db, a Shell project with 5,712 GitHub stars. SynthScan v2.0 examined 4,660 lines of code across 13 source files, recording 48 pattern matches distributed across 5 syntactic categories. The overall adjusted score of 17.5 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).

17.5
Adjusted Score
17.5
Raw Score
100%
Time Factor
2026-08-02
Last Push
5.7K
Stars
Shell
Language
4.7K
Lines of Code
13
Files
48
Pattern Hits
2026-08-02
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 20LOW 28

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

Decorative Section Separators18 hits · 54 pts
SeverityFileLineSnippetContext
MEDIUMsyno_hdd_db.sh3#--------------------------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh16#--------------------------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh403#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh667#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh757#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh949#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh1441#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh1714#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh1920 #------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh1934 #------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh1949 #------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh1963 #------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh1969#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh2271#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh2330#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_db.sh2785#------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_shutdown.sh3#------------------------------------------------------------------------------------COMMENT
MEDIUMsyno_hdd_shutdown.sh8#------------------------------------------------------------------------------------COMMENT
Redundant / Tautological Comments24 hits · 20 pts
SeverityFileLineSnippetContext
LOWsyno_hdd_db.sh380# Check if script is running in an interactive shell or from scheduleCOMMENT
LOWsyno_hdd_db.sh384 # Check if running via task schedulerCOMMENT
LOWsyno_hdd_db.sh804 # Check if we re-enabled drive db auto updatesCOMMENT
LOWsyno_hdd_db.sh1194 # Check if is NVMe or SATA M.2 SSDCOMMENT
LOWsyno_hdd_db.sh1625 # Loop through array of drives in db file checking for duplicatesCOMMENT
LOWsyno_hdd_db.sh1627 # Check if more than 1 of each drive in db fileCOMMENT
LOWsyno_hdd_db.sh1793 # Check if db file is new or old styleCOMMENT
LOWsyno_hdd_db.sh1980 # Check if section existsCOMMENT
LOWsyno_hdd_db.sh1985 # Check if already enabledCOMMENT
LOWsyno_hdd_db.sh2122 # Check if script is running from task schedulerCOMMENT
LOWsyno_hdd_db.sh2194 # Check if dtc exists and is executableCOMMENT
LOWsyno_hdd_db.sh2316 # Set HDDs to writemostly if there's also internal SSDsCOMMENT
LOWsyno_hdd_db.sh2454 # Set mem_max_mb to the amount of installed memoryCOMMENT
LOWsyno_hdd_db.sh2504 # Check if nvme support is enabledCOMMENT
LOWsyno_hdd_db.sh2519 # Check if we enabled nvme supportCOMMENT
LOWsyno_hdd_db.sh2537 # Check if m2 volume support is enabledCOMMENT
LOWsyno_hdd_db.sh2554 # Check if we enabled m2 volume supportCOMMENT
LOWsyno_hdd_db.sh2596 # Check if we disabled drive db auto updatesCOMMENT
LOWsyno_hdd_db.sh2615 # Check if we re-enabled drive db auto updatesCOMMENT
LOWsyno_hdd_db.sh2644 # Check if we disabled drive db auto updatesCOMMENT
LOWsyno_hdd_db.sh2661 # Check if we re-enabled drive db auto updatesCOMMENT
LOWsyno_hdd_db.sh2718 # Check if we edited fileCOMMENT
LOWsyno_hdd_db.sh2755 # Check if dhm_tool needs updatingCOMMENT
LOWsyno_hdd_shutdown.sh368 # Check if package is on NVMe volumeCOMMENT
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMsyno_hdd_db.sh1644# Create a backup firstCOMMENT
Excessive Try-Catch Wrapping2 hits · 2 pts
SeverityFileLineSnippetContext
MEDIUMsyno_hdd_db.sh1669 print("Error occurred: {}".format(e))CODE
LOWsyno_hdd_db.sh1668except Exception as e:CODE
Over-Commented Block3 hits · 2 pts
SeverityFileLineSnippetContext
LOWsyno_hdd_db.sh1#!/usr/bin/env bashCOMMENT
LOWsyno_hdd_db.sh321#if [[ $model =~ 'pv10-j'$ ]]; then # GitHub issue #10COMMENT
LOWsyno_hdd_shutdown.sh1#!/usr/bin/env bashCOMMENT