ghproxy

基于Go的高性能,多功能,可扩展的Github代理加速项目

Runssource: GitHubGoMPL-2.0commit 4c555ed50c55

Go, MPL-2.0 licensed. The project labels itself: devops, docker, docker proxy, github, github proxy, go, golang and proxy.

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

GHProxy 4.3.4 builds with Go 1.26.9, all 31 tests pass, the server starts and serves HTTP pages on port 8080 with logging and routing working

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.03 (measured)
recorded runs
1
last tested
stars
738
forks
125
open issues
13
watchers
4
size
1 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 ghproxy, 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 compiler not installed in container2 minutes
  • go build failed: pages/* directory missing for embed directive1 minute
  • TestExtractParts_Compatibility/Empty_path_segments failed: extractParts returned '/' instead of '' for empty first path segment1 minute
Install time
5 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
go test ./... passed all 31/31 tests, go vet passed, server binary starts and returns HTTP 200 on /, /favicon.ico, /script.js, /style.css; returns 400 on invalid proxy paths; returns 404 on unknown routes
Model tokens used
216,302
Exact commit tested
4c555ed50c55
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.

2026/10/14 20:28:07 Touka server(s) exited gracefully.
2026/10/14 20:28:07 Closing Touka logger...
Program Exit
=== Server stopped ===
Everything is working. Let me verify the full project still builds cleanly and record the final sum…
exec
/bin/sh -lc 'export PATH="/tmp/go/bin:$HOME/go/bin:$PATH" && cd /work/repo && go vet ./... 2>&1' in…
 succeeded in 2473ms:
All clean. Now let me record the final result.
tokens used
216,302
All clean. Now let me record the final result.

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 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 MPL-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.

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.03

Topics (from GitHub)

devopsdockerdocker-proxygithubgithub-proxygogolangproxyreverse-proxytouka

Embed the badge

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

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

Questions

Does ghproxy run?
Yes. ghproxy runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test ghproxy?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4c555ed50c55. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ghproxy?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ghproxy 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 ghproxy need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ghproxy?
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.
Where is the evidence for ghproxy?
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