v2ray-core

A platform for building proxies to bypass network restrictions.

Runssource: GitHubhomepageGoMITcommit d80440f3d57b

Go, MIT licensed. The project labels itself: golang, http proxy, proxy, shadowsocks, socks, socks5, v2ray and vmess.

v2ray-core runs. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

V2Ray v4.31.0 builds and runs on Go 1.22.5 in this container. All 62 non-scenario test packages pass. The binary prints its version, and all core transports (TCP, UDP, WebSocket, KCP, QUIC, TLS, XTLS, HTTP, domainsocket) and proxies (VMess, VLESS, Shadowsocks, SOCKS, Trojan, HTTP, MTProto, Blackhole, DNS, Freedom, Dokodemo) are compiled and functional.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
2
last tested
stars
46,907
forks
8,758
open issues
14
watchers
1,322
size
54 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing v2ray-core, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • qtls-go1-15 init() panics on Go 1.22+ because tls.ClientSessionState struct changed between Go 1.15 and 1.225 minutes
  • crypto/hmac: hash generation function does not produce unique values in proxy/vmess/aead/kdf.go2 minutes
  • Go 1.15 required but not installed in container1 minute
Install time
3 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
/tmp/v2ray --version returned 'V2Ray 4.31.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.22.5 linux/amd64)' with exit code 0; go test ./... excluding scenarios: 62 packages ok, 0 FAIL
Model tokens used
221,114
Exact commit tested
d80440f3d57b
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

git diff --stat HEAD 2>/dev/null' in /work/repo
 succeeded in 0ms:
V2Ray 4.31.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.22.5 linux/amd64)
A unified platform for anti-censorship.
 go.mod                  |  2 ++
 go.sum                  |  2 --
 proxy/vmess/aead/kdf.go | 16 +++++++---------
 3 files changed, 9 insertions(+), 11 deletions(-)
Here is the final report:
tokens used
221,114
Here is the final report:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 3 minutes, faster than the median of the 8 comparable projects Argusic has measured.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 9 golang projects Argusic has installed and timed, v2ray-core was the 3rd fastest to reach a running state, and 8 of 9 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 3 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.14
Argusic Runner1/3Runs100.000.08

Topics (from GitHub)

golanghttp-proxyproxyshadowsockssockssocks5v2rayvmess

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/v2ray-core.svg)](https://argusic.com/subject/v2ray-core)

Questions

Does v2ray-core run?
Yes. v2ray-core runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test v2ray-core?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d80440f3d57b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test v2ray-core?
The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does v2ray-core take to install?
3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does v2ray-core need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing v2ray-core?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does v2ray-core compare with the alternatives?
Of the 9 golang projects Argusic has installed and timed, v2ray-core was the 3rd fastest to reach a running state, and 8 of 9 reached one at all.
Where is the evidence for v2ray-core?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion