/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

2dust/v2rayN

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-29T22:29:18.000Z

3mo ago

2dust/v2rayN

v2rayN is a mature, actively maintained GUI client for Windows, Linux, and macOS. It supports Xray, sing-box, and other cores, has a large user base, and shows very recent upstream activity, so forks are most interesting if they add platform-specific UI changes, core integration work, packaging improvements, or configuration/proxy behavior tweaks.

Loading tags...

Stars100,086

Forks14,410

Default branchmaster

Last pushed2026-03-29T07:13:29Z

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

6 of 6 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if its Windows-specific fixes match your network setup; otherwise upstream is the safer default because it is far more current and actively maintained.

Choose this fork only if you need the Hiddify-specific Windows workflow and can accept substantial lag behind upstream. If you want current protocol support, active maintenance, or cross-platform parity, upstream v2rayN is the safer choice.

Prefer upstream unless you need this fork's exact legacy/custom routing and configuration behavior. This fork looks useful for niche, path-dependent deployments, but its age and divergence make it a poor default choice for new installs.

Choose this fork only if Trojan support on this older codebase is the main requirement. For most users, upstream v2rayN is the better default because this fork is stale and materially behind on newer features and fixes.

Choose this fork if you want an upstream-current v2rayN with promotions and automatic updates stripped out; skip it if you rely on built-in update convenience or want the broader upstream ecosystem.

Choose this fork only if you specifically want a Windows-only, heavily customized variant and can accept major upstream lag. For most adopters, upstream v2rayN is the safer choice because it is active, broader in platform support, and much more current.

Fork comparison

Pawdroid/shadowrocket_for_windows

38/100

stale

significant_divergence

Choose this fork only if its Windows-specific fixes match your network setup; otherwise upstream is the safer default because it is far more current and actively maintained.

Likely purpose

A Windows-focused V2Ray client fork that adds custom proxy/core behavior and a few practical connection fixes, likely aimed at users who want a more opinionated or legacy-compatible build than the fast-moving upstream.

Best for

Windows users who specifically need the fork's PPPoE, tun-mode, or xhttp workarounds.; Users who want a V2Ray client with custom behavior already baked in rather than tracking upstream closely.; Adopters willing to trade freshness for a fork that may preserve older workflows or defaults.

Additional features

Added Hysteria2 support using sing-box.
Added delay checking and core restart behavior in tun mode.
Fixed proxy settings for PPPoE connections and removed the sysproxy.exe workaround.
Added xhttp-specific protections, including download protection, dialer proxy fixes, and split-address protection.
Added Xray browser header masquerading and legacy process-name tun protection.
Added support for editing/adjusting core-related behavior and custom config handling.

Missing features

Falls behind upstream by about 200 commits, so it likely misses recent upstream core support, protocol fixes, and UI updates from March 2026.
Upstream is actively maintained with recent fixes for xhttp and hysteria2 settings that this fork does not show.
The fork's last shown activity is from November 2023, so ongoing packaging, localization, and workflow improvements from upstream are likely absent or outdated.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
Some upstream operational features such as auth, admin, or session handling may be reduced or absent.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Adds Windows-oriented proxy and tun-mode behavior that may help with tricky network setups.
Includes protocol and core support that was valuable when upstream was older.
May appeal to users who want a smaller, more self-contained fork with custom defaults.

Risks

Maintenance appears stale, so security, compatibility, and protocol regressions may linger.
Large divergence makes upstream merges harder and increases the chance of breakage.
Being materially behind upstream means newer core behavior and UI fixes may be missing.
The fork description suggests bundled/free-server behavior, which may be less transparent or less configurable than upstream.

2dust/v2rayN · Discofork