free-proxy-list

🚀 The Best Free HTTP, SOCKS4/SOCKS5, SSL,SS/SSR Proxy List,V2Ray/XRay(Vmess/Vless) Configs, Tuic, Wireguard, Hyeseria, mtproto(Telegram),Trojan-Go/Trojan-GFW Servers - 🔄 Updated Every 30 Minutes⏰

Runssource: GitHubhomepageGoMITcommit 364a694e6f6f

Go, MIT licensed. The project labels itself: anonymous proxy, free proxy list, http proxy, hyeseria, hyeseria2, mtproto, proxy checker and proxy list.

free-proxy-list runs. An Argusic agent installed it in 14 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

On Go 1.27.3 installed to ~/.local, ./gfp built and ran against live sources, completing with exit 0 and writing 2,262,680 proxy lines across 17 protocol files plus an updated README table and total.svg.

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.04 (measured)
recorded runs
1
last tested
stars
440
forks
61
open issues
2
watchers
9
size
37 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 free-proxy-list, 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.

  • Go toolchain not installed in container (no go binary, no apt without root)6 minutes
  • Version truth: README says lists update hourly but repo action runs every hour, not relevant to run; first scratch run put README one level above list dir, so app's README rewrite silently no-op'd (error swallowed by _ = os.WriteFile)3 minutes
Install time
14 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test -count=1 ./... exited 0 (13 tests passed, 0 failed); ./gfp -dir /tmp/gfp-run2 exited 0; wc -l list/*.txt summed 2262680; README table showed Last Updated: 2026-10-21 17:22:19 UTC; total.svg aria-label total: 2262680
Model tokens used
138,816
Exact commit tested
364a694e6f6f
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

The end of the recording

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

- Verified output content: entries look schema-valid (e.g. `http://IP:port`, `ssr://...` base64 pay…
- Note for a fresh user: `go` is not bundled in the container; the README doesn't publish install s…
tokens used
138,816
All done — the reported data is in the result JSON.
**Summary of what happened**
- Go wasn't present in the container; I installed the official `go1.27.3` tarball into `~/.local` (…
- `go build -v -o gfp cmd/main.go` exited 0 — the project builds.
- `go test -count=1 ./...` → `ok .../internal`, 13 test functions/subtests passed, 0 failed (`cmd` …
- Ran the real binary (`gfp -dir ...`) against the live `sources/` URLs: exit 0, produced 17 protoc…
- Verified output content: entries look schema-valid (e.g. `http://IP:port`, `ssr://...` base64 pay…
- Note for a fresh user: `go` is not bundled in the container; the README doesn't publish install s…

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 14 minutes.
  • Recovered from all 2 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 Runner1/3Runs100.000.04

Topics (from GitHub)

anonymous-proxyfree-proxy-listhttp-proxyhyeseriahyeseria2mtprotoproxy-checkerproxy-listproxy-listsshadowsockssocks-proxysocks4-proxysocks5-proxyssl-proxytrojan-gotuicv2rayvlessvmesswireguard

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/free-proxy-list.svg)](https://argusic.com/subject/free-proxy-list)

Questions

Does free-proxy-list run?
Yes. free-proxy-list runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test free-proxy-list?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 364a694e6f6f. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test free-proxy-list?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does free-proxy-list take to install?
14 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 free-proxy-list need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing free-proxy-list?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for free-proxy-list?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion