XTLS/Xray-core

Choose this fork if you are building on Amnezia’s VPN stack or need its custom VLESS/config integration. Choose upstream if you want the freshest Xray-core fixes, broader ecosystem compatibility, and lower maintenance overhead.

Prefer this fork only if you specifically need its older transport tweaks and are prepared to maintain a highly divergent codebase. For most adopters, upstream is the safer choice because this fork is stale, far behind, and likely missing many recent fixes and features.

Choose this fork only if you specifically need its older custom behavior and are prepared to live without upstream progress. For most adopters, upstream is the safer and more current choice.

Prefer this fork only if you need its local DNS/platform tweaks and are willing to absorb upstream lag. If you want the latest protocol fixes, transport work, and broad ecosystem compatibility, upstream is the safer choice.

Prefer this fork if you want a Hiddify-focused, operationally tuned Xray-core and do not need the latest upstream fixes. Prefer upstream if you care about current protocol/transport work, lower maintenance risk, or long-term compatibility.

Prefer this fork if you need its added protocol/API behavior and can tolerate substantial divergence from upstream. Prefer upstream if you want the latest fixes, broader transport completeness, and lower maintenance risk.

Choose this fork if GOST support is the main requirement and you can absorb maintenance risk. Avoid it if you need close upstream compatibility, current protocol fixes, or a low-risk production base.

Prefer this fork if you need ANYTLS/TUIC work or the Shadowsocks changes and can tolerate feature removal and protocol churn. Prefer upstream if you need the broadest compatibility, especially Hysteria2 support.