claudia
Deploy Node.js projects to AWS Lambda and API Gateway easily
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 9d68ed4c62e1
JavaScript, MIT licensed. The project labels itself: api gateway, aws, aws lambda, claudia, javascript, nodejs and serverless.
claudia runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install succeeds, 356 offline unit tests pass (0 failures), the CLI help and module load work; AWS-integration tests are skipped because real AWS credentials are not available in this container.
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
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.
- fs.mkdtempSync(os.tmpdir()) in spec/fs-promise-spec.js fails with EACCES on Node 18 because the template lacks 'XXXXXX' suffix15 minutes
- unzip binary is not installed in the container, causing zipdir spec to fail with ENOENT10 minutes
- npm 9 generates lockfileVersion 3 (packages key) but collect-files-spec expected lockfileVersion 1 (dependencies key)5 minutes
- Install time
- under a minute
- Cold machine to finish
- 41 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- node run-clean.js ci exited 0, 356 of 356 specs passed, 0 failures; node bin/cmd.js --help printed usage; require('./index.js') loaded 14 commands
- Model tokens used
- 305,093
- Exact commit tested
- 9d68ed4c62e1
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Fixes applied**: 3 errors hit, all fixed.
- **Error 1**: `fs.mkdtempSync(os.tmpdir())` lacks trailing `XXXXXX` template chars required by Nod…
- **Error 2**: `unzip` binary not in container. Replaced `child_process.execFile('unzip', ...)` wit…
- **Error 3**: npm 9 writes `lockfileVersion: 3` (uses `packages` key, not `dependencies`). Fixed `…
tokens used
305,093
All 356 specs pass (0 failures), the CLI binary works, and the module loads correctly. Let me compi…
**Install**: `npm ci` succeeded at 20:08:33 — deps installed, project builds.
**Fixes applied**: 3 errors hit, all fixed.
- **Error 1**: `fs.mkdtempSync(os.tmpdir())` lacks trailing `XXXXXX` template chars required by Nod…
- **Error 2**: `unzip` binary not in container. Replaced `child_process.execFile('unzip', ...)` wit…
- **Error 3**: npm 9 writes `lockfileVersion: 3` (uses `packages` key, not `dependencies`). Fixed `…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 0 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 3 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 5 api-gateway projects Argusic has installed and timed, claudia was the 1st fastest to reach a running state, and 4 of 5 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.20 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/claudia)Questions
- Does claudia run?
- claudia runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test claudia?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9d68ed4c62e1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test claudia?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does claudia take to install?
- 0 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 claudia need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing claudia?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does claudia compare with the alternatives?
- Of the 5 api-gateway projects Argusic has installed and timed, claudia was the 1st fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for claudia?
- 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.