setup-php
GitHub action to set up PHP with extensions, php.ini configuration, coverage drivers, and various tools.
Runssource: GitHubhomepageTypeScriptMITcommit f3d967b8bc6d
TypeScript, MIT licensed. The project labels itself: code coverage, composer, continuous integration, github actions, php, php extensions, static analysis and tools.
setup-php runs. An Argusic agent installed it in 6 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed and the project builds under Node v24.22.2; the full jest suite (605 tests, 9 suites) passes with exit 0 and 100% coverage; the compiled action bundles and starts correctly but the PHP system install is blocked by the container lacking root/sudo.
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 91 of 100 (the mean of this project's run scores).
At a glance
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.
- node dist/index.js: action starts but cannot install PHP in this container - src/scripts/linux.sh:288 fails 'sudo: command not found' and apt-get install sudo fails (no root), so run loops until 300s timeout (exit 124)14 minutes
- npm test under container Node 18.19.1: 11 failures with TypeError: releases.toSorted is not a function (src/tools.ts:252,221; repo requires Node>=20, CI pins 24.x)8 minutes
- Install time
- 6 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- npm test (Node v24.22.2) exited 0: 9 suites passed, 605 passed / 605 total, coverage 100%; npm run build, typecheck, eslint, format-check all exited 0. node dist/index.js launched (printed '==> Setup PHP') and stopped at 'sudo: command not found' (exit 124 via timeout).
- Model tokens used
- 54,894
- Exact commit tested
- f3d967b8bc6d
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Installed per the README/CONTRIBUTING: `npm install`, `npm run build`, `npm test`. - Hit one reproducible error: the repo requires Node ≥ 20 (`Array.prototype.toSorted` in `src/tools… - After the fix: `npm test` → 9 suites passed, 605/605 tests passed, exit 0, 100% coverage; `build`… - Launching the actual action (`node dist/index.js`) starts it correctly (`==> Setup PHP`), but the… tokens used 54,894 All verification is complete. The final result has been reported via the `ARGUSIC_RESULT:` line abo… In short: - Installed per the README/CONTRIBUTING: `npm install`, `npm run build`, `npm test`. - Hit one reproducible error: the repo requires Node ≥ 20 (`Array.prototype.toSorted` in `src/tools… - After the fix: `npm test` → 9 suites passed, 605/605 tests passed, exit 0, 100% coverage; `build`… - Launching the actual action (`node dist/index.js`) starts it correctly (`==> Setup PHP`), but the…
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 6 minutes.
- 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
- Hit 2 errors during setup, 1 of which were not solved.
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 6 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 90.00 | 0.08 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
code-coveragecomposercontinuous-integrationgithub-actionsphpphp-extensionsstatic-analysistools
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/setup-php)Questions
- Does setup-php run?
- Yes. setup-php runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test setup-php?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f3d967b8bc6d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test setup-php?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does setup-php take to install?
- 6 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 setup-php need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing setup-php?
- 2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for setup-php?
- 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.