v2fly/v2ray-core

Choose this fork if you need SagerNet-specific functionality and can tolerate divergence and maintenance lag. Choose upstream if you want current fixes, broader compatibility, and lower operational risk.

Choose this fork if your goal is a router-centric V2Ray build with OSPF and ROS-oriented workflows. Choose upstream if you want the broadest compatibility, fresher fixes, and the least maintenance risk.

Choose this fork if you value the extra fixes and transport compatibility more than staying close to upstream. Avoid it if you need maximum upstream parity, packaging stability, or minimal maintenance risk.

Choose this fork only if you specifically want its older deployment and compatibility changes; otherwise upstream is the better default because it is much newer, more actively maintained, and has far more recent fixes and features.

Choose upstream unless you specifically want the fork's README/ad branding. This fork offers no evident runtime advantages and is behind on upstream fixes and features.

Prefer this fork only if you need its fork-specific management and forwarding features and are willing to own an old, highly diverged codebase. For most adopters, upstream is the safer default because this fork is stale and likely missing many recent fixes and protocol improvements.

Choose this fork only if you specifically want its Merlin/embedded packaging and are willing to accept major upstream drift. For most adopters, upstream is the safer choice because it is actively maintained and materially newer.

Prefer upstream unless you specifically need this fork as a working copy; it adds no visible features and is already behind on recent upstream fixes.

Prefer upstream unless you specifically depend on this fork’s older, customized behavior. This fork looks abandoned enough that adopting it without an internal maintenance owner would be risky.