reqwest

An easy and powerful Rust HTTP Client

Runssource: GitHubhomepageRustApache-2.0commit aff2ddb677e2

Rust, Apache-2.0 licensed. The project labels itself: http, http client and rust.

reqwest runs. An Argusic agent installed it in 0.7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

reqwest builds and all 101 tests pass with default features (rustls, charset, http2, system-proxy) on Rust 1.98.1.

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.06 (measured)
recorded runs
2
last tested
stars
11,927
forks
1,450
open issues
493
watchers
83
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.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Disk full (7.8 GB root) when compiling with optional features (blocking, cookies, gzip, brotli, deflate, zstd, multipart). Linker failed with 'No space left on device' during cargo test on extended feature set.
Install time
under a minute
Cold machine to finish
37 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
cargo test --lib --test client --test redirect --test timeouts --test retry --test connector_layers --test not_tcp --test ci --test upgrade ran 101 tests; 101 passed, 3 ignored (TLS-gated), 0 failed
Model tokens used
155,266
Exact commit tested
aff2ddb677e2
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.

| lib (unit tests) | 46 | All passed |
| client | 18 passed, 1 ignored | Passed |
| ci | 1 | Passed |
| connector_layers | 9 | Passed |
| not_tcp | 2 passed, 1 ignored | Passed |
| redirect | 13 passed, 1 ignored | Passed |
| retry | 4 | Passed |
| timeouts | 7 | Passed |
| upgrade | 1 | Passed |
All 9 default-feature test binaries: 101/101 tests passed (3 ignored, TLS-gated).
**Disk space issue**: The container has a 7.8 GB root filesystem. When compiling with optional feat…
**Verification**: Tests exercise real HTTP behavior against local loopback servers spun up per-test…

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 0.7 minutes, faster than the median of the 8 comparable projects Argusic has measured.
  • 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.
  • Measured 2 times, so the result is not a one-off.

Of the 9 http projects Argusic has installed and timed, reqwest was the 3rd fastest to reach a running state, and 9 of 9 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.
  • A quick evaluation: it was running 0.7 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 Runner2/3Runs100.000.06
Argusic Runner1/3Ran out of time0.000.18

Topics (from GitHub)

httphttp-clientrust

Embed the badge

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

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

Questions

Does reqwest run?
Yes. reqwest runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test reqwest?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit aff2ddb677e2. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test reqwest?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does reqwest take to install?
0.7 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 reqwest need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing reqwest?
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.
How does reqwest compare with the alternatives?
Of the 9 http projects Argusic has installed and timed, reqwest was the 3rd fastest to reach a running state, and 9 of 9 reached one at all.
Where is the evidence for reqwest?
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