Repository Analysis

itzg/docker-minecraft-server

Docker image that provides a Minecraft Server for Java Edition that automatically installs/upgrades versions, modloaders, modpacks and more at startup

9.7 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of itzg/docker-minecraft-server, a Shell project with 13,956 GitHub stars. SynthScan v2.0 examined 12,139 lines of code across 299 source files, recording 88 pattern matches distributed across 6 syntactic categories. The overall adjusted score of 9.7 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).

9.7
Adjusted Score
9.7
Raw Score
100%
Time Factor
2026-07-13
Last Push
14.0K
Stars
Shell
Language
12.1K
Lines of Code
299
Files
88
Pattern Hits
2026-07-14
Scan Date
0.01
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

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

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 1HIGH 3MEDIUM 8LOW 76

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

Over-Commented Block74 hits · 58 pts
SeverityFileLineSnippetContext
LOWexamples/docker-compose-curseforge-atm7.yaml1####################################################################COMMENT
LOWexamples/docker-compose-curseforge-atm7.yaml21# Example: 'name:' or 'mc_atm6:' #COMMENT
LOWexamples/docker-compose-curseforge-atm7.yaml41# #COMMENT
LOWexamples/docker-compose-curseforge-atm7.yaml61# This section defines what folders and volumes you want to give #COMMENT
LOWexamples/docker-compose-curseforge-atm7.yaml81# #COMMENT
LOWexamples/docker-compose-curseforge-atm7.yaml101 CF_SERVER_MOD: /modpacks/ATM7-0.4.32-server.zipCOMMENT
LOWexamples/docker-compose-curseforge-atm7.yaml121# Example: Add full timestamp to logs #COMMENT
LOWexamples/lazymc/docker_compose.yml1# Lazymc requires that the minecraft server have a static IP.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml1####################################################################################################COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml21####################################################################################################COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml41# - When this is set to 'false', commands using a player's username will not work unless the playerCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml61# - The various options are explained in more detail on the wiki:COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml81# |COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml101COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml121COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml141 connection-timeout: 5000 # 5 secondsCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml161 # - Change this if you want to use different tables for different servers.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml201# | | #COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml221watch-files: trueCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml241# installed.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml301COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml321# - Possible options:COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml341COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml361# chat.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml381#COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml421COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml441# If a final sort according to "inheritance rules" should be performed after the traversal algorithmCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml461context-satisfy-mode: at-least-one-value-per-keyCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml481apply-global-groups: trueCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml501COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml521# assignments.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml541COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml561# considering if a player should have access to a certain permission.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml581# world_the_end: worldCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml601# +----------------------------------------------------------------------------------------------+ #COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml621# disabled.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml641# However, if you're willing to accept the consequences, the catch can be disabled by setting thisCOMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml681# +----------------------------------------------------------------------------------------------+ #COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml721# If LuckPerms should attempt to resolve Vanilla command target selectors for LP commands.COMMENT
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml741# LuckPerms will still act as the permission manager, but server administrators will be unable toCOMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml1####################################################################################################COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml21# +----------------------------------------------------------------------------------------------+ #COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml41# - To get around this, you can use a player's uuid directly in the command, or enable this option.COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml61#COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml81# | and all stored in the same file by switching to a combined storage variant.COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml101 # - This must be created already. Don't worry about this setting if you're using MongoDB.COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml121 # - For maximum performance and responsiveness to spike demands, it is recommended to not setCOMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml141 # This setting allows you to define extra properties for connections.COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml161COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml201# | These options are documented on greater detail on the wiki under "Instant Updates". | #COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml221# Define which messaging service should be used by the plugin.COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml241# below.COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml281# +----------------------------------------------------------------------------------------------+ #COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml301COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml321# the arguments given within the command.COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml341COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml361#COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml381#COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml421#COMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml441# Defines the mode used to determine whether a set of contexts are satisfied.COMMENT
14 more matches not shown…
AI Response Leakage3 hits · 22 pts
SeverityFileLineSnippetContext
HIGHexamples/docker-compose-curseforge-atm7.yaml69# In this example the volume name is 'data'. When docker creates #COMMENT
HIGHexamples/docker-compose-curseforge-atm7.yaml71# end of the container name specified above. In this example it #COMMENT
HIGHexamples/auto-curseforge/atm8/docker-compose.yml39 # In this example, the left-side needs to be the same as /data volume of mc serviceCOMMENT
Self-Referential Comments6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMexamples/docker-compose-curseforge-atm7.yaml50# Define a restart policy here. #COMMENT
MEDIUM…pply-extra-configs/shared-configs/LuckPerms/config.yml90# The following block defines the settings for remote database storage methods.COMMENT
MEDIUM…pply-extra-configs/shared-configs/LuckPerms/config.yml96 # Define the address and port for the database.COMMENT
MEDIUM…/multi-project/servers/mc-plugins/LuckPerms/config.yml88# The following block defines the settings for remote database storage methods.COMMENT
MEDIUM…/multi-project/servers/mc-plugins/LuckPerms/config.yml94 # Define the address and port for the database.COMMENT
MEDIUMexamples/spiget/docker-compose.yml2# This file is purposely named spiget with an "e" since it provides an example of theCOMMENT
Hallucination Indicators1 hit · 10 pts
SeverityFileLineSnippetContext
CRITICALdocs/versions/java.md104 at MC-BOOTSTRAP/org.spongepowered.mixin/org.spongepowered.asm.mixin.transformer.MixinPreProcessorStandard.transformMethCODE
Slop Phrases2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUM…pply-extra-configs/shared-configs/LuckPerms/config.yml43# - To get around this, you can use a player's uuid directly in the command, or enable this option.COMMENT
MEDIUM…/multi-project/servers/mc-plugins/LuckPerms/config.yml41# - To get around this, you can use a player's uuid directly in the command, or enable this option.COMMENT
AI Slop Vocabulary2 hits · 3 pts
SeverityFileLineSnippetContext
LOW…pply-extra-configs/shared-configs/LuckPerms/config.yml323# => parents-by-weight just use the users most highly weighted parentCOMMENT
LOW…/multi-project/servers/mc-plugins/LuckPerms/config.yml310# => parents-by-weight just use the users most highly weighted parentCOMMENT