Repository Analysis

docker-mailserver/docker-mailserver

Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container.

6.7 Low AI signal View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of docker-mailserver/docker-mailserver, a Shell project with 18,588 GitHub stars. SynthScan v2.0 examined 21,542 lines of code across 182 source files, recording 91 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 6.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).

6.7
Adjusted Score
6.7
Raw Score
100%
Time Factor
2026-07-06
Last Push
18.6K
Stars
Shell
Language
21.5K
Lines of Code
182
Files
91
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

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 0HIGH 0MEDIUM 25LOW 66

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 91 distinct pattern matches across 8 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 Block55 hits · 55 pts
SeverityFileLineSnippetContext
LOWcompose.yaml21 - /etc/localtime:/etc/localtime:roCOMMENT
LOWtest/config/junk-mailbox/user-patches.sh1#!/bin/bashCOMMENT
LOWtest/config/dovecot-lmtp/user-patches.sh21# unix_listener lmtp {COMMENT
LOWtest/config/user-patches/user-patches.sh1#!/bin/bashCOMMENT
LOWtest/config/rspamd_full/user-patches.sh1#!/bin/bashCOMMENT
LOWtest/helper/log_and_filtering.bash1#!/bin/bashCOMMENT
LOWtest/helper/change-detection.bash1#!/bin/bashCOMMENT
LOWtest/helper/common.bash1#!/bin/bashCOMMENT
LOWtest/helper/common.bash21 load "${REPOSITORY_ROOT}/test/helper/log_and_filtering"COMMENT
LOWtest/helper/common.bash41# If neither an explicit non-empty argument is given nor `CONTAINER_NAME`COMMENT
LOWtest/helper/common.bash101# Execute a command inside the container with name ${CONTAINER_NAME}. The commandCOMMENT
LOWtest/helper/common.bash121COMMENT
LOWtest/helper/sending.bash1#!/bin/bashCOMMENT
LOWtest/helper/sending.bash21# The very first parameter **may** be `--expect-rejection` - use it of you expect the mail transaction to not finishCOMMENT
LOWtest/helper/sending.bash101 echo "${output}"COMMENT
LOWtest/helper/setup.bash1#!/bin/bashCOMMENT
LOWtest/helper/setup.bash41COMMENT
LOWtest/helper/setup.bash81# - Use `local <VARIABLE>` to override within a specific test case.COMMENT
LOWtest/helper/setup.bash101 export TEST_FILES_VOLUME="${REPOSITORY_ROOT}/test/files:${TEST_FILES_CONTAINER_PATH}:ro"COMMENT
LOWtest/helper/tls.bash1#!/bin/bashCOMMENT
LOWconfig-examples/user-patches.sh1#!/bin/bashCOMMENT
LOWtarget/scripts/check-for-changes.sh1#!/bin/bashCOMMENT
LOWtarget/scripts/startup/variables-stack.sh41COMMENT
LOWtarget/scripts/startup/setup.d/dovecot.sh21 # https://doc.dovecot.org/2.3/settings/core/#core_setting-hostnameCOMMENT
LOWtarget/scripts/startup/setup.d/mail_state.sh121 # NOTE: The Postfix spool location has mixed owner/groups to take into account:COMMENT
LOWtarget/scripts/helpers/relay.sh1#!/bin/bashCOMMENT
LOWtarget/scripts/helpers/relay.sh21#COMMENT
LOWtarget/scripts/helpers/relay.sh41# There is a minor chance of a lookup occurring during a rebuild of these files that may affect or delay delivery?COMMENT
LOWtarget/scripts/helpers/relay.sh101 'smtp_tls_security_level = encrypt'COMMENT
LOWtarget/scripts/helpers/relay.sh201}COMMENT
LOWtarget/scripts/helpers/relay.sh221# relay-service.test relay-account:relay-passCOMMENT
LOWtarget/scripts/helpers/relay.sh241# setup /etc/postfix/relayhost_mapCOMMENT
LOWtarget/scripts/helpers/relay.sh261# smtp_tls_security_level = encryptCOMMENT
LOWtarget/scripts/helpers/relay.sh281COMMENT
LOWtarget/scripts/helpers/relay.sh301# https://www.mailjet.com/blog/news/which-smtp-port-mailjet/#port-465COMMENT
LOWtarget/scripts/helpers/relay.sh321# and incorrectly describe how they deliver mail:COMMENT
LOWtarget/scripts/helpers/relay.sh341#COMMENT
LOWtarget/scripts/helpers/utils.sh101 fiCOMMENT
LOWtarget/scripts/helpers/utils.sh121# If you want to set a new value for `readme_directory` in Postfix's `main.cf`,COMMENT
LOWtarget/scripts/helpers/ssl.sh161 local SCOPE_SSL_TYPE="TLS Setup [SSL_TYPE=${SSL_TYPE}]"COMMENT
LOWtarget/scripts/helpers/ssl.sh321 fiCOMMENT
LOWtarget/scripts/helpers/dns.sh1#!/bin/bashCOMMENT
LOWtarget/scripts/helpers/dns.sh21 # TODO: `OVERRIDE_HOSTNAME` was introduced for non-Docker runtimes that could not configure an explicit hostname.COMMENT
LOWtarget/scripts/helpers/dns.sh41 # Emulates the intended behaviour of `hostname -d`:COMMENT
LOWtarget/scripts/helpers/log.sh21LCYAN=$(echo -ne '\e[1;36m')COMMENT
LOWtarget/scripts/helpers/rspamd.sh81 #COMMENT
LOWtarget/scripts/helpers/postfix.sh1#!/bin/bashCOMMENT
LOWtarget/scripts/helpers/postfix.sh81 [[ ${ACCOUNT_PROVISIONER} == 'LDAP' ]] && echo "${DOMAINNAME}" >>"${TMP_VHOST}"COMMENT
LOW…get/scripts/helpers/database/manage/postfix-virtual.sh1#!/bin/bashCOMMENT
LOWdocs/content/faq.md421 Edit the system cron file `nano ./docker-data/dms/cron/sa-learn`, and set an appropriate configuration:COMMENT
LOW…content/config/advanced/mail-forwarding/relay-hosts.md121 ```cf-extraCOMMENT
LOW…cs/content/examples/use-cases/ios-mail-push-support.md141 # 2. You don't need your mailboxes to synchronize immediately since they are automatically synchronized when opeCOMMENT
LOW.github/FUNDING.yml1github: [georglauterbach]COMMENT
LOW.github/workflows/docs-preview-deploy.yml101 with:COMMENT
LOW.github/workflows/docs-preview-deploy.yml121 # Disable adding a comment about successful deployment status to the PR.COMMENT
Self-Referential Comments16 hits · 48 pts
SeverityFileLineSnippetContext
MEDIUMtest/helper/common.bash16# This function is internal and should not be used in tests.COMMENT
MEDIUMtest/helper/common.bash54# This function is internal and should not be used in tests.COMMENT
MEDIUMtest/helper/setup.bash17# This function is internal and should not be used in tests.COMMENT
MEDIUMtest/helper/setup.bash56# Create a dedicated configuration directory for a test file.COMMENT
MEDIUMtarget/scripts/startup/variables-stack.sh20# This function handles variables that are deprecated. This allows aCOMMENT
MEDIUMtarget/scripts/startup/variables-stack.sh193# This function handles environment variables related to LDAP.COMMENT
MEDIUMtarget/scripts/startup/variables-stack.sh211# This function handles environment variables related to SASLAUTHDCOMMENT
MEDIUMtarget/scripts/startup/setup.d/getmail.sh14 # Create the directory /etc/getmailrc.d to place the user config in later.COMMENT
MEDIUMtarget/scripts/startup/setup.d/saslauthd.sh13 # Create a config based on ENVCOMMENT
MEDIUMtarget/scripts/startup/setup.d/fetchmail.sh71 # Create a new fetchmail config for this poll entry:COMMENT
MEDIUMtarget/scripts/startup/setup.d/security/rspamd.sh3# This file is executed during startup of DMS. Hence, the `index.sh` helper has alreadyCOMMENT
MEDIUMtarget/scripts/startup/setup.d/security/rspamd.sh270# This function handles setup of the Hfilter module (seeCOMMENT
MEDIUMtarget/scripts/startup/setup.d/security/rspamd.sh296# This function handles setup of the neural module (seeCOMMENT
MEDIUMtarget/scripts/helpers/relay.sh125 # Create the relayhost_map config file:COMMENT
MEDIUMtarget/scripts/helpers/log.sh29# This function provides the logging for scripts used by DMS.COMMENT
MEDIUMtarget/scripts/helpers/rspamd.sh20# Create a temporary log file (with `mktemp`) that one can filter to searchCOMMENT
Decorative Section Separators6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMtarget/scripts/start-mailserver.sh10# ------------------------------------------------------------COMMENT
MEDIUMtarget/scripts/start-mailserver.sh12# ------------------------------------------------------------COMMENT
MEDIUMtarget/scripts/start-mailserver.sh29# ------------------------------------------------------------COMMENT
MEDIUMtarget/scripts/start-mailserver.sh33# ------------------------------------------------------------COMMENT
MEDIUMtarget/scripts/start-mailserver.sh163# ------------------------------------------------------------COMMENT
MEDIUMtarget/scripts/start-mailserver.sh167# ------------------------------------------------------------COMMENT
Redundant / Tautological Comments6 hits · 9 pts
SeverityFileLineSnippetContext
LOWtest/helper/change-detection.bash80 # Read file in reverse, collect lines until match with sed is found,COMMENT
LOWtest/helper/common.bash383# Check if a container is running.COMMENT
LOWtarget/scripts/startup/setup.d/getmail.sh17 # Check if custom getmailrc_general.cf file is present.COMMENT
LOWtarget/scripts/startup/setup.d/security/rspamd.sh279 # Check if we received a number firstCOMMENT
LOWtarget/scripts/helpers/utils.sh155# Check if an environment variable's value is zero or one. This aids in checking variablesCOMMENT
LOWtarget/scripts/helpers/utils.sh178# Check if an environment variable's value is an integer.COMMENT
AI Slop Vocabulary3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUMtest/helper/common.bash27# test suite more robust as we can be sure that the container name isCOMMENT
MEDIUMtarget/scripts/helpers/relay.sh117# By sender: `sender_dependent_default_transport_maps = texthash:/etc/postfix/sender_transport_map` (the current opt-oCOMMENT
MEDIUM…et/scripts/helpers/database/manage/postfix-accounts.sh48# Dovecot Master account support can leverage the same management logic:COMMENT
Fake / Example Data3 hits · 3 pts
SeverityFileLineSnippetContext
LOWtest/files/emails/quota-exceeded.txt6Lorem ipsum dolor sit amet. Et quidem architecto id Quis saepe vel corporis odit aut nesciunt nisi. Et voluptatem exerciCODE
LOWtest/files/emails/quota-exceeded.txt6Lorem ipsum dolor sit amet. Et quidem architecto id Quis saepe vel corporis odit aut nesciunt nisi. Et voluptatem exerciCODE
LOWdocs/content/config/security/ssl.md454 LETSENCRYPT_mail_EMAIL='admin@example.com'CODE
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWconfig-examples/user-patches.sh6# If you modify any supervisord configuration, make sure to runCOMMENT
Deep Nesting1 hit · 1 pts
SeverityFileLineSnippetContext
LOWtarget/bin/acme_extract.py22CODE