static-curl

Static cURL with latest features

Runssource: GitHubShellMITcommit 22338b1f21b8

Shell, MIT licensed. The project labels itself: curl, ech, http client, http3 and http3 client.

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

A statically linked curl 8.23.0 binary (OpenSSL 4.0.3, HTTP/3, ECH, brotli, zstd, c-ares, libidn2, libpsl, libssh2, nghttp2/3, ngtcp2) was built from this repo's script in the container and fetched http://example.com/ over HTTPS with HTTP/3, returning HTTP 200, and 1790 of 1809 upstream curl tests passed.

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.29 (measured)
recorded runs
2
last tested
stars
519
forks
57
open issues
1
watchers
8
size
0 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 static-curl, 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.

  • wget was not installed and the script's download step needs a wget with HTTPS (wget built without TLS refused `wget https://...` with 'HTTPS support not compiled in')12 minutes
  • autotools (m4, autoconf, automake, libtool/autoreconf) and makeinfo were missing; libpsl configure died on PKG_PROG_PKG_CONFIG (pkg.m4) and curl's autoreconf needs the full stack10 minutes
  • The script hardcodes clang/clang-20 (apt metadata) but no clang exists in the container; clang-20 not found aborted OpenSSL and CXX=clang++-20 aborted zstd CMake9 minutes
  • README standard path `sh curl-static-cross.sh` requires Docker (missing) and apt/root (no sudo, apt lock Permission denied)8 minutes
  • curl's own test suite failed 19 tests, all IPv6 tests
Install time
46 minutes
Cold machine to finish
54 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
`/tmp/final-release/bin/curl-linux-x86_64-glibc -V` printed 'curl 8.23.0 ... OpenSSL/4.0.3 ... Features: ... ECH HTTP3 ...', static (ldd: 'not a dynamic executable'); `.../curl-linux-x86_64-glibc -sS -o /tmp/curl_test.html -w 'http_code=%{http_code} http_version=%{http_version}' https://example.com/` returned 'http_code=200 ... http_version=3', exit 0; `make test` in curl-8.23.0 returned exit 2 with 'TESTDONE: 1790 tests out of 1809 reported OK: 98%', all 19 failures IPv6-only (no IPv6 in container)
Model tokens used
1,112,451
Exact commit tested
22338b1f21b8
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: real HTTPS 200s (HTTP/3 negotiated), and curl's own suite `make test` → 1790/1809 OK (9…
Note for the shop: `test_depth` is `tier1_real` (real end-to-end HTTPS + test suite), `install_minu…
exec
/bin/sh -lc "echo \"start check: first log file mtime 14:00/14:01, now 14:52\"; stat -c '%y' /tmp/s…
 succeeded in 0ms:
start check: first log file mtime 14:00/14:01, now 14:52
2026-10-19 14:01:04.629215991 +0000
2026-10-19 14:52:54
The mission is complete. Here is the final report as the required single plain-text line:
tokens used
1,112,451
The mission is complete. Here is the final report as the required single plain-text line:

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.
  • Recovered from all 5 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.

What did not, or is not known

  • Took 46 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.

Of the 6 curl projects Argusic has installed and timed, static-curl was the 6th fastest to reach a running state, and 6 of 6 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.

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.29
Argusic Runner1/3Ran out of time0.000.59

Topics (from GitHub)

curlechhttp-clienthttp3http3-client

Embed the badge

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

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

Questions

Does static-curl run?
Yes. static-curl runs. Argusic installed and launched it on a clean machine in 46 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test static-curl?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 22338b1f21b8. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test static-curl?
The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does static-curl take to install?
46 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 static-curl need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing static-curl?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does static-curl compare with the alternatives?
Of the 6 curl projects Argusic has installed and timed, static-curl was the 6th fastest to reach a running state, and 6 of 6 reached one at all.
Where is the evidence for static-curl?
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