wormhole

Open-source ngrok alternative. Expose your localhost to the internet with one command. Built with Go + Cloudflare Workers.

Runs with mockssource: GitHubhomepageGoMITcommit c53fd29e3eb4

Go, MIT licensed. The project labels itself: cli, cloudflare, developer tools, go, localhost, networking, ngrok and reverse proxy.

wormhole runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Wormhole CLI builds and runs (version prints wormhole c53fd29), its Go tests pass, the edge relay's 34 tests pass on Node 22, and a locally-run tunnel client connected to a mock relay, forwarded a POST through to a local origin server (201 response with hello-from-local:/probe?q=1:POST), and recorded the request in the traffic inspector API.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.13 (measured)
recorded runs
1
last tested
stars
439
forks
33
open issues
2
watchers
8
size
3 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 wormhole, 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.

  • Relay URL hardcoded as wss://relay.wormhole.bar with no override; /etc/hosts not writable so a local schema-correct mock relay could not be reached10 minutes
  • Go toolchain missing (go 1.26.1+ required by README, none installed)3 minutes
  • Edge test suite crashed on Node 18 with ReferenceError: File is not defined (undici needs Node >=20)2 minutes
Install time
15 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
go test ./... -race exited 0 (client, inspect, server, transport ok); npm test in edge exited 0 (2 files, 34 passed); end-to-end: launched ./wormhole http 9800 --headless with WORMHOLE_RELAY_URL=ws://127.0.0.1:8789/_wormhole/register against a local protocol-correct mock relay, simulated a visitor request via a second WS client (POST /probe?q=1, body payload-abc base64), the client returned http_response status 201 with decoded body hello-from-local:/probe?q=1:POST, and curl http://127.0.0.1:4040/api/requests returned the full recorded entry with status 201; curl -o /dev/null -w %{http_code} http://127.0.0.1:4040/ returned 200
Model tokens used
616,759
Exact commit tested
c53fd29e3eb4
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

Mission complete. Summary of what happened:
- **Install**: No Go (needs 1.26.1+) and Node was v18 (too old for the edge tests). Installed Go 1.…
- **Tests**: `go test ./... -race` all ok; `cd edge && npm test` → 34/34 passed.
- **E2E**: Added a minimal `WORMHOLE_RELAY_URL` override (the relay URL was hardcoded with no way t…
- **Result line**: printed above as `ARGUSIC_RESULT: {…}` (tier2_mock — the public relay needs real…
tokens used
616,759
Mission complete. Summary of what happened:
- **Install**: No Go (needs 1.26.1+) and Node was v18 (too old for the edge tests). Installed Go 1.…
- **Tests**: `go test ./... -race` all ok; `cd edge && npm test` → 34/34 passed.
- **E2E**: Added a minimal `WORMHOLE_RELAY_URL` override (the relay URL was hardcoded with no way t…
- **Result line**: printed above as `ARGUSIC_RESULT: {…}` (tier2_mock — the public relay needs real…

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

  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 15 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 128 cli projects Argusic has installed and timed, wormhole was the 116th fastest to reach a running state, and 117 of 128 reached one at all.

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/3Runs with mocks92.000.13

Topics (from GitHub)

clicloudflaredeveloper-toolsgolocalhostnetworkingngrokreverse-proxytunnelwebsocket

Embed the badge

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

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

Questions

Does wormhole run?
wormhole runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test wormhole?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c53fd29e3eb4. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test wormhole?
The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does wormhole take to install?
15 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 wormhole need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing wormhole?
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 wormhole compare with the alternatives?
Of the 128 cli projects Argusic has installed and timed, wormhole was the 116th fastest to reach a running state, and 117 of 128 reached one at all.
Where is the evidence for wormhole?
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