Discofork
Repository brief

2dust/v2rayNG

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-30T11:58:48.385Z
3mo ago

2dust/v2rayNG

v2rayNG is a large, actively maintained Android client for V2Ray, with support for Xray core and v2fly core. It is popular and highly forked, which makes it a plausible fork target if you care about Android proxy client maintenance, core updates, or UI/behavior changes.

GitHub
Loading tags...
Stars52,974
Forks7,091
Default branchmaster
Last pushed2026-03-29T11:33:16Z
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

9 of 9 fork briefs
Selected

Choose this fork if you want MahsaNG’s added workflows and bundled convenience features. Choose upstream v2rayNG if you care more about staying current with the latest fixes, core updates, and a simpler maintenance path.

Choose this fork only if its custom core and behavior changes match a specific need; otherwise upstream is the safer default because it is far more active and much closer to current development.

Choose this fork only if you want its customized legacy behavior and are willing to own the maintenance gap. For most users, upstream v2rayNG is the safer choice because this fork is materially stale and heavily diverged.

Choose this fork if you value its server-management and UI workflow changes more than staying current with upstream. Choose upstream if you want the most active maintenance and the newest fixes.

Choose this fork only if its specific config and subscription behavior matches your needs. If you want current maintenance, upstream v2rayNG is the safer default.

Prefer upstream unless you specifically need this fork's customization set. Choose the fork only if its TV/deeplink/package-name behavior is important enough to accept a stale, highly divergent codebase.

Choose this fork only if its added protocol/config behavior matters more than staying close to upstream. For most adopters who want an actively maintained v2rayNG, upstream is the safer default.

Choose this fork if your priority is Android TV usability and you want a customized client tuned for that environment. Choose upstream if you want current maintenance, broad device fit, and easier long-term updates.

Choose this fork only if its config and subscription workflow changes match your needs and you are comfortable adopting an older, diverged base. If you want the latest upstream fixes and broad compatibility, upstream v2rayNG is the safer choice.