magic-nix-cache-action
Save 30-50%+ of CI time without any effort or cost. Use Magic Nix Cache, a totally free and zero-configuration binary cache for Nix on GitHub Actions.
Could not verifysource: GitHubTypeScriptMITcommit 84c0677f58dc
TypeScript, MIT licensed. The project labels itself: caching, continuous integration and nix.
Argusic could not get magic-nix-cache-action running. An Argusic agent installed it in 1.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
npm install, npm run build (tsup), npm run package (ncc), npm run lint all pass; executing the action emits the expected Nix-not-installed warning and exits 0
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 80 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.
- Install time
- 1 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npx tsup build succeeded (ESM 16KB, DTS), ncc package succeeded (6.7MB), eslint passed, and node dist/index.js with GITHUB_ACTIONS=true, RUNNER_ARCH=X64, RUNNER_OS=Linux, and INPUT__INTERNAL-STRICT-MODE=true ran cleanly and printed the expected 'no-op mode because Nix is not installed' warning
- Model tokens used
- 182,210
- Exact commit tested
- 84c0677f58dc
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **`npm run build`** (tsup): succeeded -- compiled `src/` → `dist/index.js` (16 KB ESM + types). - **`npm run package`** (ncc): succeeded -- bundled into `dist/index.js` (6.7 MB). - **`npm run lint`** (eslint): passed clean. - **`prettier --check src/`**: all source files properly formatted. - **Executing the action** (simulating GitHub Actions environment): the process identified that Nix… **Errors encountered and fixed:** | Error | Fix | |---|---| | `SyntaxError: Invalid regular expression flags` (`/v` and `/iv` regex flags unsupported in Node 1… | `RUNNER_ARCH and/or RUNNER_OS is not defined` | Set `RUNNER_ARCH=X64 RUNNER_OS=Linux` | | `Input does not meet YAML 1.2 "Core Schema"` for `_internal-strict-mode` | Provided boolean input… | `Input does not meet YAML 1.2 "Core Schema"` for `diff-store` | Provided `INPUT_DIFF-STORE=false`…
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 1.2 minutes.
- Nothing broke on the way: zero errors between clone and running.
- 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
- An agent with no time limit did not get it running.
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 | Unverified | 80.00 | 0.02 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.03 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/magic-nix-cache-action)Questions
- Does magic-nix-cache-action run?
- Argusic could not verify that magic-nix-cache-action runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test magic-nix-cache-action?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 84c0677f58dc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test magic-nix-cache-action?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does magic-nix-cache-action take to install?
- 1.2 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 magic-nix-cache-action need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing magic-nix-cache-action?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for magic-nix-cache-action?
- 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.