Home / acmesh-official / acme.sh
Repository Analysis

acmesh-official/acme.sh

A pure Unix shell script ACME client for SSL / TLS certificate automation

4.4 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of acmesh-official/acme.sh, a Shell project with 47,169 GitHub stars. SynthScan v2.0 examined 65,076 lines of code across 307 source files, recording 159 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 4.4 places this repository in the Likely human-written 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).

4.4
Adjusted Score
4.4
Raw Score
100%
Time Factor
2026-07-14
Last Push
47.2K
Stars
Shell
Language
65.1K
Lines of Code
307
Files
159
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 0HIGH 3MEDIUM 40LOW 116

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

Decorative Section Separators25 hits · 87 pts
SeverityFileLineSnippetContext
MEDIUMdeploy/truenas_ws.sh15# ------------------------------------------------COMMENT
MEDIUM⚡deploy/byteplus_alb.sh49# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh51# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh56# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh58# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh190 # ── 5. Save new CertificateId for next renewal ───────────────────────────────COMMENT
MEDIUM⚡deploy/byteplus_alb.sh198# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh200# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh212# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh214# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh224# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUM⚡deploy/byteplus_alb.sh226# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMdeploy/byteplus_alb.sh12# ┌─────────────────────────────────────────────────────────────────────┐COMMENT
MEDIUMdeploy/byteplus_alb.sh23# └─────────────────────────────────────────────────────────────────────┘COMMENT
MEDIUMdeploy/byteplus_alb.sh73 # ── 1. Load & validate credentials ──────────────────────────────────────────COMMENT
MEDIUMdeploy/byteplus_alb.sh138 # ── 2. Build certificate name ────────────────────────────────────────────────COMMENT
MEDIUMdeploy/byteplus_alb.sh163 # ── 3. Read cert and key ─────────────────────────────────────────────────────COMMENT
MEDIUMdeploy/byteplus_alb.sh174 # ── 4. Deploy: first-time upload or renewal replace ─────────────────────────COMMENT
MEDIUMdeploy/byteplus_alb.sh254# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMdeploy/byteplus_alb.sh256# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMdeploy/byteplus_alb.sh274# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMdeploy/byteplus_alb.sh276# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMdeploy/byteplus_alb.sh388# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMdeploy/byteplus_alb.sh390# ══════════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMdnsapi/dns_inwx.sh13# -------------COMMENT
Over-Commented Block71 hits · 70 pts
SeverityFileLineSnippetContext
LOWnotify/smtp.sh1#!/usr/bin/env shCOMMENT
LOWnotify/bark.sh1#!/usr/bin/env shCOMMENT
LOWnotify/dingtalk.sh41 # DINGTALK_SIGNING_KEY=""COMMENT
LOWnotify/aws_ses.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/vault.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/directadmin.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/edgio.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/haproxy.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/haproxy.sh21# It is strongly recommended to set this something that makes senseCOMMENT
LOWdeploy/haproxy.sh41#COMMENT
LOWdeploy/consul.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/vault_cli.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/multideploy.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/multideploy.sh21# 0 means success, otherwise error.COMMENT
LOWdeploy/multideploy.sh181COMMENT
LOWdeploy/localcopy.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/cpanel_uapi.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/netlify.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/keyhelp.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/lighttpd.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/lighttpd.sh21# It is strongly recommended to set this something that makes senseCOMMENT
LOWdeploy/unifi.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/unifi.sh21# The deploy-hook automatically detects standard Unifi installationsCOMMENT
LOWdeploy/unifi.sh41# (same setting as above, default is updated when running on Cloud Key Gen1):COMMENT
LOWdeploy/windows_rdp.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/windows_rdp.sh101 cat <<PSEOFCOMMENT
LOWdeploy/ssh.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/ssh.sh21# export DEPLOY_SSH_FULLCHAIN=""COMMENT
LOWdeploy/panos.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/zyxel_gs1900.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/zyxel_gs1900.sh21# Current GS1900 Switch Compatibility:COMMENT
LOWdeploy/zyxel_gs1900.sh41#COMMENT
LOWdeploy/mydevil.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/truenas_ws.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/truenas_ws.sh21# export DEPLOY_TRUENAS_HOSTNAME="<TRUENAS_HOSTNAME_OR_IP>"COMMENT
LOWdeploy/truenas_ws.sh101# 0: trueCOMMENT
LOWdeploy/truenas_ws.sh141 doneCOMMENT
LOWdeploy/synology_dsm.sh1#!/bin/bashCOMMENT
LOWdeploy/synology_dsm.sh21# - export SYNO_HOSTNAME="localhost" - defaults to "localhost"COMMENT
LOWdeploy/proxmoxve.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/gcore_cdn.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/ruckus.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/truenas.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/ali_dcdn.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/cleverreach.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/routeros.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/routeros.sh21# deploy script to work.COMMENT
LOWdeploy/routeros.sh41# could be updated. Currently only the www-ssl service is beeingCOMMENT
LOWdeploy/proxmoxbs.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/qiniu.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/ali_cdn.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/byteplus_alb.sh1#!/usr/bin/env shCOMMENT
LOWdeploy/byteplus_alb.sh21# │ → ReplaceCertificate (UpdateMode=new) — single API call │COMMENT
LOWdeploy/byteplus_alb.sh41# - ReplaceCertificate with UpdateMode=new uploads + replaces in 1 callCOMMENT
LOWdeploy/peplink.sh1#!/usr/bin/env shCOMMENT
LOW.github/workflows/wiki-guard.yml1name: Wiki GuardCOMMENT
LOWdnsapi/dns_bunny.sh161## _sub_domain="_acme-challenge.two"COMMENT
LOWdnsapi/dns_dgon.sh161##################### Private functions below #####################COMMENT
LOWdnsapi/dns_arubabusiness.sh21COMMENT
LOWdnsapi/dns_arubabusiness.sh81COMMENT
11 more matches not shown…
Redundant / Tautological Comments29 hits · 45 pts
SeverityFileLineSnippetContext
LOWdeploy/kemplm.sh55 # Check if certificate is already installedCOMMENT
LOWdeploy/haproxy.sh262 # Check if issuer cert is also a root CA certCOMMENT
LOW⚡deploy/multideploy.sh82 # Check if yq is installedCOMMENT
LOW⚡deploy/multideploy.sh89 # Check if deploy file existsCOMMENT
LOWdeploy/multideploy.sh147 # Check if extracted services exist in services listCOMMENT
LOWdeploy/multideploy.sh150 # Check if service existsCOMMENT
LOWdeploy/kong.sh61 #Check if sslcreated (if not => POST else => PATCH)COMMENT
LOWdeploy/lighttpd.sh210 # Check if issuer cert is also a root CA certCOMMENT
LOWdeploy/truenas.sh219 # Check if the app use the same certificate TrueNAS web UICOMMENT
LOW⚡deploy/byteplus_alb.sh185 # Check if deploy step set _new_cert_idCOMMENT
LOWdnsapi/dns_sotoon.sh63 # Check if there are existing TXT records for this subdomainCOMMENT
LOWdnsapi/dns_sotoon.sh78 # Check if this exact TXT value already exists (avoid duplicates)COMMENT
LOWdnsapi/dns_sotoon.sh143 # Check if there are existing TXT records for this subdomainCOMMENT
LOWdnsapi/dns_sotoon.sh211 # Check if the response contains our domainCOMMENT
LOWdnsapi/dns_sotoon.sh225 # Check if the hyphenated name exists in the responseCOMMENT
LOWdnsapi/dns_sotoon.sh229 # Check if the origin itself is used as nameCOMMENT
LOWdnsapi/dns_infoblox_uddi.sh63 # Check if record already existsCOMMENT
LOWdnsapi/dns_infoblox_uddi.sh178 # Check if response contains results (even if empty)COMMENT
LOWdnsapi/dns_bunny.sh22 # Check if API Key is setCOMMENT
LOWdnsapi/dns_bunny.sh79 # Check if API Key ExistsCOMMENT
LOWdnsapi/dns_subreg.sh116# Check if the current $response contains a successful status in the ns2:Map format:COMMENT
LOWdnsapi/dns_cyon.sh229 # Check if we got an error response (JSON) instead of HTMLCOMMENT
LOWdnsapi/dns_dgon.sh21 # Check if API Key ExistsCOMMENT
LOWdnsapi/dns_dgon.sh76 # Check if API Key ExistsCOMMENT
LOWdnsapi/dns_one.sh33 #Check if the TXT existsCOMMENT
LOWdnsapi/dns_one.sh71 #Check if the TXT existsCOMMENT
LOWdnsapi/dns_huaweicloud.sh162 # Check if retry count is reachedCOMMENT
LOWdnsapi/dns_huaweicloud.sh247 # Check if record existCOMMENT
LOWdnsapi/dns_mgwm.sh76 # Check if credentials are setCOMMENT
Self-Referential Comments13 hits · 39 pts
SeverityFileLineSnippetContext
MEDIUMacme.sh7614 # Create the custom cert home now instead of on first issuance, so theCOMMENT
MEDIUMdeploy/haproxy.sh199 # Create a temporary PEM fileCOMMENT
MEDIUMdeploy/lighttpd.sh147 # Create a temporary PEM fileCOMMENT
MEDIUMdeploy/panos.sh27# This function is to parse the XML response from the firewallCOMMENT
MEDIUMdeploy/panos.sh58#This function is used to deploy to the firewallCOMMENT
MEDIUMdnsapi/dns_bunny.sh14## Create the text record for validation.COMMENT
MEDIUMdnsapi/dns_bhosted.sh349# Create a unique config key for cached record idsCOMMENT
MEDIUMdnsapi/dns_dgon.sh13## Create the text record for validation.COMMENT
MEDIUMdnsapi/dns_ali.sh13# This file is referenced by Alibaba Cloud Services deploy hooksCOMMENT
MEDIUMdnsapi/dns_online.sh159 # Creating a dummy record in this temporary version, because online.net doesn't accept enabling an empty versionCOMMENT
MEDIUMdnsapi/dns_mgwm.sh16# This function is called by acme.sh to add a TXT record.COMMENT
MEDIUMdnsapi/dns_mgwm.sh36# This function is called by acme.sh to remove a TXT record after validation.COMMENT
MEDIUMdnsapi/dns_mgwm.sh87 # Create the Basic Auth Header. acme.sh's _base64 function is used for encoding.COMMENT
Example Usage Blocks15 hits · 23 pts
SeverityFileLineSnippetContext
LOW⚡deploy/multideploy.sh79# Usage:COMMENT
LOWdeploy/multideploy.sh121# Usage:COMMENT
LOWdeploy/multideploy.sh175# Usage:COMMENT
LOWdeploy/multideploy.sh203# Usage:COMMENT
LOWdeploy/multideploy.sh223# Usage:COMMENT
LOWdeploy/multideploy.sh265# Usage:COMMENT
LOWdeploy/zyxel_gs1900.sh37# Usage:COMMENT
LOWdeploy/truenas_ws.sh30# Usage:COMMENT
LOWdeploy/truenas_ws.sh92# Usage:COMMENT
LOWdeploy/truenas_ws.sh113# Usage:COMMENT
LOWdnsapi/dns_bookmyname.sh25# Usage:COMMENT
LOWdnsapi/dns_eurodns.sh20# Usage:COMMENT
LOWdnsapi/dns_glesys.sh20# Usage:COMMENT
LOWdnsapi/dns_glesys.sh71# Usage:COMMENT
LOWdnsapi/dns_laodc.sh12# Usage:COMMENT
Magic Placeholder Names3 hits · 20 pts
SeverityFileLineSnippetContext
HIGHdnsapi/dns_ipprojects.sh54 _err "e.g.: export IPP_Apikey=\"your_api_key\""CODE
HIGHdnsapi/dns_eurodns.sh22# export EURODNS_API_KEY="your-api-key"COMMENT
HIGHdnsapi/dns_laodc.sh13# export LaoDC_Key="your-api-key"COMMENT
Excessive Try-Catch Wrapping2 hits · 4 pts
SeverityFileLineSnippetContext
MEDIUMnotify/smtp.sh344 print("Error sending: %r" % err)CODE
MEDIUMnotify/smtp.sh348 print("Error connecting to %s:%d: %r" % (smtp_host, smtp_port, err))CODE
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWdnsapi/dns_namecheap.sh15# Due to Namecheap's API limitation all the records of your domain will be read and re applied, make sure to have a backCOMMENT