Docker image that provides a Minecraft Server for Java Edition that automatically installs/upgrades versions, modloaders, modpacks and more at startup
This report summarizes scanner evidence for itzg/docker-minecraft-server, a Shell project with 14,406 GitHub stars. SynthScan examined 12,781 lines of code across 314 source files, recording 89 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 9.3 (Moderate pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 88 finding(s).
Are imports declared and package/API names verified? 1 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 89 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 89 distinct pattern matches across 6 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. 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 configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| 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 | 34 | # 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 | 109 | 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 |
| LOW | .github/workflows/verify-pr.yml | 58 | # make sure to track the base image version in build.yml | 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 |