v2ray/v2ray-core

Prefer upstream unless you explicitly need this fork’s old patches. This fork is best viewed as a legacy, specialized snapshot with a few local fixes, not as an actively maintained alternative.

Adopt this fork only if its DNS/fake-IP and router behavior are exactly what you need. For most users, the stale activity and large divergence from upstream make it a poor default choice compared with the actively maintained upstream line.

Prefer this fork only if you need its legacy Android packaging or the JSON-loader customization and can accept substantial upstream drift. For most adopters, upstream or a newer maintained fork is the safer choice.

Prefer upstream unless you need this exact fork’s historical state. The fork shows little functional differentiation, little maintenance activity, and some lag relative to upstream, so it is a weak choice for new adopters.

Prefer this fork only if its fake-IP/DNS changes are exactly what you need and you can tolerate an old upstream base. For general adoption, upstream is the safer choice because this fork is stale and likely missing a large amount of later work.

Choose this fork only if its panel integration and traffic-limiting behavior are exactly what you need. For most adopters, upstream or a more current descendant will be safer and easier to maintain.

Prefer upstream unless you specifically need this older snapshot; the fork adds no visible value and appears abandoned.

Choose this fork only if built-in rate limiting is the main requirement; otherwise upstream is likely the safer base because this fork is very stale and materially behind.