Discofork
Repository brief

v2fly/v2ray-core

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:43:24.880Z
1mo ago

v2fly/v2ray-core

v2fly/v2ray-core is an actively maintained Go repository for building proxy/network tools to bypass network restrictions and protect privacy. It has a large user and fork base, recent commits in March 2026, and a broad codebase organized around core, app, proxy, transport, common, and infra packages.

GitHub
Loading tags...
Stars33,479
Forks5,011
Default branchmaster
Last pushed2026-03-26T22:52:10Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork only if you specifically need its VLESS-centric behavior or existing deployment compatibility. If you want current upstream fixes, active maintenance, or broad protocol support, upstream is the safer choice.

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.