castor
🦫 A lightweight and modern task runner for Automation, CI/CD & DevOps.
Runssource: GitHubhomepagePHPMITcommit 56cd0342f2d1
PHP, MIT licensed. The project labels itself: cli, command line, command line tool, hacktoberfest, php library, task runner and tool.
castor runs. An Argusic agent installed it in 35 minutes and hit 9 errors on a clean machine with no GPU, and the whole session was recorded.
Castor v1.8.1 installed as static binary at /home/runner/.local/bin/castor; PHP 8.4.23 with sodium, zip, curl, openssl at /home/runner/php/8.4.23/bin/php and /tmp/php (static-php-cli bulk build); Composer dependencies installed at /work/repo/vendor; zip/ssh/scp binaries available on PATH; test suite runs with 321 passing, 5 environment-specific failures and 1 Docker-not-available error.
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 88.9 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.
- sodium PHP extension missing in containerbase PHP build10 minutes
- PHP 8.4+ not installed in container; no system PHP available8 minutes
- ssh/scp not installed (SSH tests fail)5 minutes
- zip binary not installed (archive:zip-binary test fails)1 minute
- WaitForDockerTest requires Docker daemon — not available in container
- Notify* tests fail: no desktop notification system in headless container
- Install time
- 35 minutes
- Cold machine to finish
- 55 minutes
- Errors hit and fixed
- 9 hit, 4 fixed with no human help
- How the result was proved
- php vendor/bin/phpunit --no-coverage --exclude-group=slow,network: Tests: 335, Assertions: 1219, Errors: 1, Failures: 5, Skipped: 8
- Model tokens used
- 914,959
- Exact commit tested
- 56cd0342f2d1
- 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.
succeeded in 196071ms: Tests: 335, Assertions: 1219, Errors: 1, Failures: 5, Skipped: 8. exec /bin/sh -lc 'find /work/repo -maxdepth 1 -name "*.deb" -empty -delete 2>/dev/null; ls /work/repo/*.… succeeded in 0ms: DONE Let me do one final structural check on what we have: The 5 failures and 1 error are all environmental (no Docker daemon, no desktop notifications, `ls` … tokens used 914,959 Let me do one final structural check on what we have: The 5 failures and 1 error are all environmental (no Docker daemon, no desktop notifications, `ls` …
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.
What did not, or is not known
- Took 35 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
- Hit 9 errors during setup, 5 of which were not solved.
- 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, castor was the 126th fastest to reach a running state, and 117 of 128 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
Topics (from GitHub)
clicommand-linecommand-line-toolhacktoberfestphp-librarytask-runnertool
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/castor)Questions
- Does castor run?
- Yes. castor runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 9 errors on the way, and recorded the session.
- How did Argusic test castor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 56cd0342f2d1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test castor?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does castor take to install?
- 35 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 castor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing castor?
- 9 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 castor compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, castor was the 126th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for castor?
- 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.