Docker image that provides a Minecraft Server for Java Edition that automatically installs/upgrades versions, modloaders, modpacks and more at startup
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).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | examples/docker-compose-curseforge-atm7.yaml | 1 | #################################################################### | COMMENT |
| LOW | examples/docker-compose-curseforge-atm7.yaml | 21 | # Example: 'name:' or 'mc_atm6:' # | COMMENT |
| LOW | examples/docker-compose-curseforge-atm7.yaml | 41 | # # | COMMENT |
| LOW | examples/docker-compose-curseforge-atm7.yaml | 61 | # This section defines what folders and volumes you want to give # | COMMENT |
| LOW | examples/docker-compose-curseforge-atm7.yaml | 81 | # # | COMMENT |
| LOW | examples/docker-compose-curseforge-atm7.yaml | 101 | CF_SERVER_MOD: /modpacks/ATM7-0.4.32-server.zip | COMMENT |
| LOW | examples/docker-compose-curseforge-atm7.yaml | 121 | # Example: Add full timestamp to logs # | COMMENT |
| LOW | examples/lazymc/docker_compose.yml | 1 | # Lazymc requires that the minecraft server have a static IP. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 1 | #################################################################################################### | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 21 | #################################################################################################### | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 41 | # - When this is set to 'false', commands using a player's username will not work unless the player | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 61 | # - The various options are explained in more detail on the wiki: | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 81 | # | | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 101 | COMMENT | |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 121 | COMMENT | |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 141 | connection-timeout: 5000 # 5 seconds | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 161 | # - Change this if you want to use different tables for different servers. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 201 | # | | # | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 221 | watch-files: true | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 241 | # installed. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 301 | COMMENT | |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 321 | # - Possible options: | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 341 | COMMENT | |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 361 | # chat. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 381 | # | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 421 | COMMENT | |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 441 | # If a final sort according to "inheritance rules" should be performed after the traversal algorithm | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 461 | context-satisfy-mode: at-least-one-value-per-key | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 481 | apply-global-groups: true | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 501 | COMMENT | |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 521 | # assignments. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 541 | COMMENT | |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 561 | # considering if a player should have access to a certain permission. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 581 | # world_the_end: world | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 601 | # +----------------------------------------------------------------------------------------------+ # | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 621 | # disabled. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 641 | # However, if you're willing to accept the consequences, the catch can be disabled by setting this | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 681 | # +----------------------------------------------------------------------------------------------+ # | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 721 | # If LuckPerms should attempt to resolve Vanilla command target selectors for LP commands. | COMMENT |
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 741 | # LuckPerms will still act as the permission manager, but server administrators will be unable to | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 1 | #################################################################################################### | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 21 | # +----------------------------------------------------------------------------------------------+ # | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 41 | # - 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.yml | 61 | # | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 81 | # | and all stored in the same file by switching to a combined storage variant. | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 101 | # - 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.yml | 121 | # - For maximum performance and responsiveness to spike demands, it is recommended to not set | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 141 | # This setting allows you to define extra properties for connections. | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 161 | COMMENT | |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 201 | # | These options are documented on greater detail on the wiki under "Instant Updates". | # | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 221 | # Define which messaging service should be used by the plugin. | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 241 | # below. | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 281 | # +----------------------------------------------------------------------------------------------+ # | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 301 | COMMENT | |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 321 | # the arguments given within the command. | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 341 | COMMENT | |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 361 | # | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 381 | # | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 421 | # | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 441 | # Defines the mode used to determine whether a set of contexts are satisfied. | COMMENT |
| 14 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | examples/docker-compose-curseforge-atm7.yaml | 69 | # In this example the volume name is 'data'. When docker creates # | COMMENT |
| HIGH | examples/docker-compose-curseforge-atm7.yaml | 71 | # end of the container name specified above. In this example it # | COMMENT |
| HIGH | examples/auto-curseforge/atm8/docker-compose.yml | 39 | # In this example, the left-side needs to be the same as /data volume of mc service | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | examples/docker-compose-curseforge-atm7.yaml | 50 | # Define a restart policy here. # | COMMENT |
| MEDIUM | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 90 | # The following block defines the settings for remote database storage methods. | COMMENT |
| MEDIUM | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 96 | # Define the address and port for the database. | COMMENT |
| MEDIUM | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 88 | # The following block defines the settings for remote database storage methods. | COMMENT |
| MEDIUM | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 94 | # Define the address and port for the database. | COMMENT |
| MEDIUM | examples/spiget/docker-compose.yml | 2 | # This file is purposely named spiget with an "e" since it provides an example of the | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| CRITICAL | docs/versions/java.md | 104 | at MC-BOOTSTRAP/org.spongepowered.mixin/org.spongepowered.asm.mixin.transformer.MixinPreProcessorStandard.transformMeth | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 43 | # - 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.yml | 41 | # - To get around this, you can use a player's uuid directly in the command, or enable this option. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …pply-extra-configs/shared-configs/LuckPerms/config.yml | 323 | # => parents-by-weight just use the users most highly weighted parent | COMMENT |
| LOW | …/multi-project/servers/mc-plugins/LuckPerms/config.yml | 310 | # => parents-by-weight just use the users most highly weighted parent | COMMENT |