compose-action

This action runs your docker-compose file and clean up before action finished

Runs with mockssource: GitHubhomepageTypeScriptMITcommit 4596b50939ca

TypeScript, MIT licensed. The project labels itself: continuous integration, docker compose, github actions and open source.

compose-action runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Full source compiles, packages, and passes all 72 unit tests with 100% branch/line/function coverage. The GitHub Action is ready for use in a CI runner with Docker available.

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
211
forks
31
open issues
0
watchers
1
size
19 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 compose-action, 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.

  • Node 18 insufficient; project requires >=241 minute
  • Stale node_modules_bak polluted vitest discovery (23 false test failures)0.5 minutes
Install time
3 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm run test:ci exited 0; 9 test files, 72 tests passed, 100% coverage (lines/branches/functions). npm run build (tsc --noEmit) passed. npm run package built dist/index.js and dist/post.js successfully.
Model tokens used
53,614
Exact commit tested
4596b50939ca
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
Behaviour against real services
this run was verified against stand-in services only

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 1, 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.

**Verification**: The project is a GitHub Action (requires `@actions/core` runtime + Docker daemon)…
**Errors encountered**:
- Container had Node 18, project requires >=24 — fixed by downloading Node 24 to a local path.
- A stale `node_modules_bak` directory from earlier `npm install` (before Node upgrade) was polluti…
tokens used
53,614
All systems green. Here's the final assessment:
**Install**: `npm install` succeeded after upgrading Node from 18→24. Build (`tsc --noEmit`), lint,…
**Verification**: The project is a GitHub Action (requires `@actions/core` runtime + Docker daemon)…
**Errors encountered**:
- Container had Node 18, project requires >=24 — fixed by downloading Node 24 to a local path.
- A stale `node_modules_bak` directory from earlier `npm install` (before Node upgrade) was polluti…

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

  • Installed in 3 minutes, faster than the median of the 3 comparable projects Argusic has measured.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 4 continuous-integration projects Argusic has installed and timed, compose-action was the 2nd fastest to reach a running state, and 1 of 4 reached one at all.

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 Runner1/3Runs with mocks92.000.06

Topics (from GitHub)

continuous-integrationdocker-composegithub-actionsopen-source

Embed the badge

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

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

Questions

Does compose-action run?
compose-action runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test compose-action?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4596b50939ca. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test compose-action?
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 compose-action take to install?
3 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 compose-action need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing compose-action?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does compose-action compare with the alternatives?
Of the 4 continuous-integration projects Argusic has installed and timed, compose-action was the 2nd fastest to reach a running state, and 1 of 4 reached one at all.
Where is the evidence for compose-action?
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.

Discussion