gps949/Mirage
stale
significant_divergence
Selected Choose this fork if the WebUI and operator workflow matter more than staying close to upstream Headscale. Choose upstream if you want current fixes, active maintenance, and the lowest compatibility risk.
parvin528/headscale
stale
significant_divergence
Prefer this fork only if its packaging and local control-plane changes match a specific deployment need and you are willing to own long-term rebasing. For most adopters, upstream Headscale is the safer choice because this fork is significantly diverged and behind on recent fixes.
nullroute-commits/headscale
stale
significant_divergence
Choose upstream instead unless you specifically need this exact historical revision; this fork adds nothing observable and is behind on recent fixes and operational improvements.
yangchuansheng/headscale
stale
significant_divergence
Choose upstream Headscale unless you specifically need this fork's older customizations or are prepared to maintain a divergent codebase. The fork looks substantially stale and heavily modified, so it is better suited to niche adopters than to anyone wanting the safest default deployment.
meson800/headscale
stale
significant_divergence
Prefer upstream unless you specifically need one of the fork’s custom auth or release behaviors and are willing to maintain a deeply divergent codebase yourself.
cmars/headscale
stale
significant_divergence
Choose this fork only if you specifically want a legacy Headscale snapshot or are willing to maintain a large rebase yourself. For normal self-hosted tailnet use, upstream is the better choice because this fork is far behind and appears stale.
pecigonzalo/headscale
slowing
significant_divergence
Choose this fork only if you want a bespoke Headscale branch and are prepared to verify core tailnet behavior yourself. If your priority is stability and upstream compatibility, the divergence and removed coverage are significant red flags.
cylonix/headscale
active
significant_divergence
Choose this fork if multi-tenancy and the added admin/tooling surface matter more than staying close to upstream. Avoid it if you need maximum upstream compatibility or a low-risk, drop-in Headscale deployment.
POWERFULMOVES/PMOVES-headscale
Prefer this fork only if you specifically need PMOVES.AI-oriented docs or agent hints. If you want improved Headscale capabilities, the fork offers little beyond upstream and is materially behind it.
yuanzhou029/headscale
slowing
significant_divergence
Choose this fork only if its added operator/auth/storage changes matter more than staying close to upstream. If you mainly want stable Headscale compatibility and active upstream maintenance, upstream is the safer default.