guzzle

Guzzle, an extensible PHP HTTP client

Runssource: GitHubPHPMITcommit 93939470950a

PHP, MIT licensed. The project labels itself: curl, guzzle, http client, httpclient, php, psr 7, requests and webservices.

guzzle runs. An Argusic agent installed it in 8 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.

Composer dependencies installed successfully, PHP 8.3 CLI runs with all required extensions, test servers (node.js on 8126 and PHP on 10000) respond 200, PHPUnit test suite executes 3095 tests with 8550 assertions; 1 error (StreamHandlerTest credential leak test) and 1 failure (StreamHandlerTest exception type mismatch) are environment-specific differences in how localhost:123 connection failures are categorized.

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

At a glance

verdict
Runs
Argusic Score
94 / 100
cost of the verifying run
$0.16 (measured)
recorded runs
2
last tested
stars
23,445
forks
2,392
open issues
2
watchers
430
size
13 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 guzzle, 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.

  • PHP 7.4+ runtime not installed in container; no root access for apt6 minutes
  • composer install failed: guzzlehttp/test-server requires guzzlehttp/guzzle ^8.1 but root package is a dev ref2 minutes
  • HttplugIntegrationTest errors: 51 connection failures to port 10000 and 8126 test servers2 minutes
  • ctype_digit() undefined: ctype.so not loaded in static PHP build1 minute
  • StreamHandlerTest::testDoesNotLeakRequestUriCredentialsInConnectionErrorMessage errors and testAddsErrorToResponse fails: environment-specific connect behavior (localhost:123 yields RequestException instead of ConnectException)
Install time
8 minutes
Cold machine to finish
25 minutes
Errors hit and fixed
5 hit, 4 fixed with no human help
How the result was proved
vendor/bin/phpunit --no-coverage: Tests: 3095, Assertions: 8550, Errors: 1, Failures: 1, Skipped: 103
Model tokens used
471,443
Exact commit tested
93939470950a
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.

[Mon Nov  2 15:34:26 2026] 127.0.0.1:40412 Accepted
[Mon Nov  2 15:34:26 2026] 127.0.0.1:40412 [302]: GET /server.php?redirect=1
[Mon Nov  2 15:34:26 2026] 127.0.0.1:40412 Closing
Let me clean up the temp files and compile the final report.
exec
/bin/sh -lc "cd /work/repo && /tmp/php-extracted/usr/bin/php8.3 -c /tmp/php.ini -r \"echo 'PHP work…
 succeeded in 0ms:
PHP works: 8.3.6
Now let me produce the final JSON result.
tokens used
471,443
Now let me produce the final JSON 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.
  • 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 8 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
  • Hit 5 errors during setup, 1 of which were not solved.

Of the 6 curl projects Argusic has installed and timed, guzzle was the 4th 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.
  • A quick evaluation: it was running 8 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/3Runs96.000.16
Argusic Runner1/3Runs with mocks92.000.20

Topics (from GitHub)

curlguzzlehttp-clienthttpclientphppsr-7requestswebservices

Embed the badge

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

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

Questions

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