acmesh-official/acme.sh

Prefer upstream unless you specifically need this older frozen snapshot; the fork adds no visible capabilities and is far behind on maintenance.

Prefer upstream unless you specifically need this fork’s ownership context. As-is, this fork offers no visible added capability and lags far enough behind that it is better treated as a stale mirror than a differentiated alternative.

Prefer upstream unless you specifically want a slimmed-down, lightly customized fork and are willing to accept major lag and reduced validation. This fork looks best for narrow self-managed use, not for teams that want current provider support or broad operational reliability.

Prefer upstream unless you specifically need this older, unmodified snapshot. The fork shows no added capabilities and is materially stale, so it is a poor choice for users who want current acme.sh behavior or active maintenance.

Prefer the fork only if you specifically want a stripped-down, legacy-friendly client and can accept missing modern upstream capabilities. For most adopters, upstream acme.sh is the safer choice because it is actively maintained and much more complete.

Prefer upstream unless you specifically need this exact fork identity or an unchanged snapshot for Centmin Mod compatibility. For most adopters, the fork offers no visible feature gain and is materially behind upstream.

Choose this fork only if CloudHub V2 deployment is the requirement. For general acme.sh use, upstream is the safer choice because this fork is stale and heavily behind.

Prefer this fork only if the NSD `zonesdir` multi-domain behavior is the deciding requirement. For most adopters, upstream acme.sh is the better choice because this fork is far behind and appears to add only one narrow workflow fix.

Choose this fork only if domain-key reuse is the main requirement. For most adopters, upstream is the safer choice because this fork is far behind and appears effectively abandoned.