frp
A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
Runssource: GitHubGoApache-2.0commit d20a23299600
Go, Apache-2.0 licensed. The project labels itself: expose, firewall, frp, go, http proxy, nat, p2p and proxy.
frp runs. An Argusic agent installed it in 5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
frp v0.71.0 builds successfully, all 36 unit test packages pass, and frps/frpc correctly proxy TCP traffic end-to-end
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go 1.25.0 required but not installed in environment2 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- sh /tmp/e2e_test4.sh logged 'E2E_OK:b\'hello-frp-e2e\'' via TCP proxy through frps:7000 -> frpc -> echo_server:7001 on port 7002; make test returned 36 ok and 0 FAIL
- Model tokens used
- 229,465
- Exact commit tested
- d20a23299600
- 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.
-rwxrwxr-x 1 runner runner 20668576 Sep 27 07:16 frps exec /bin/sh -lc 'cd /work/repo && export GOROOT="/home/runner/go" && export GOPATH="/home/runner/gopath… succeeded in 1702ms: 36 exec /bin/sh -lc 'cd /work/repo && export GOROOT="/home/runner/go" && export GOPATH="/home/runner/gopath… exited 1 in 1548ms: All tests passed with zero failures. Let me compile the final report. tokens used 229,465 All tests passed with zero failures. Let me compile 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 5 minutes.
- Recovered from all 1 error 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 Apache-2.0, 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.
- A quick evaluation: it was running 5 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/frp)Questions
- Does frp run?
- Yes. frp runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test frp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d20a23299600. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test frp?
- 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 frp take to install?
- 5 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 frp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing frp?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for frp?
- 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.