/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

v2ray/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-30T12:59:24.529Z

3mo ago

v2ray/v2ray-core

v2ray/v2ray-core is a Go-based network-proxy core for building tools that bypass network restrictions and secure network connections. It is highly forked and starred, but the repository itself points readers to v2fly/v2ray-core, and the visible recent commit history is old relative to the current date.

Loading tags...

Stars46,963

Forks8,869

Default branchmaster

Last pushed2026-03-09T03:22:47Z

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

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if you specifically need its legacy snapshot or custom build workflow. For most adopters, upstream is the safer default because this fork is very stale and substantially diverged.

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.

Fork comparison

amazted/v2ray-core

38/100

stale

significant_divergence

Choose this fork only if you specifically need its legacy snapshot or custom build workflow. For most adopters, upstream is the safer default because this fork is very stale and substantially diverged.

Likely purpose

Provide a customized proxy-core codebase for developers who want to extend or embed an older V2Ray implementation, with substantial local editing around generated configs, tests, and release tooling.

Best for

Developers maintaining an existing deployment that already depends on this fork.; Teams that want to study or extend a legacy V2Ray codebase rather than adopt upstream.; Operators willing to trade upstream freshness for a fork-specific build or packaging workflow.

Additional features

Custom cross-platform protoc/dev tooling under `.dev/protoc/` for Linux, macOS, and Windows.
Repository-level CI/workflow customization in `.github/workflows/` and related GitHub automation files.
A fork-specific release/config packaging workflow, including `release/config/geosite.dat` changes.
Adds or extends platform-specific client support, such as mobile, Android, iOS, or desktop packaging.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.

Missing features

The fork is far behind upstream: it is 1118 commits behind and shows very large net deletions, so adopters should expect missing upstream fixes and updates.
Large deletions in generated protobuf/config files suggest some upstream config or API surfaces may no longer be present or kept current.
Tests and scenario coverage were heavily edited or removed in several places, which makes regressions harder to catch.
Upstream data/config artifacts such as geosite-based routing content appear to have been pruned or changed, which may reduce feature completeness.
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.

Strengths

May appeal to teams that need a smaller or more customized legacy proxy core.
Broad touch across build, CI, and generated files suggests the fork was adapted for its own packaging and release process.
Still clearly rooted in the V2Ray architecture, so existing proxy-oriented concepts remain recognizable.

Risks

High divergence from upstream means merge/rebase cost is likely high.
Stale activity increases the chance of unpatched bugs, protocol drift, and security issues.
Heavy deletion footprint suggests features may be incomplete, disabled, or harder to validate.
Users depending on current V2Ray behavior may find incompatibilities or missing expectations.

v2ray/v2ray-core · Discofork