Zappa
Serverless Python
Runs with mockssource: GitHubPythonMITcommit e9ecb1feea14
Python, MIT licensed. The project labels itself: alb, api gateway, aws, aws lambda, bottle, django, flask and hacktoberfest.
Zappa runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Zappa 0.62.1 installed from source in a Python 3.12 virtualenv; CLI responds with version and help; 96 unit tests pass covering handler, middleware, ASGI, async, utilities, and placebo-mocked AWS interactions.
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 56 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.
- Zappa.__init__ with load_credentials=True creates 16 boto3 clients, each taking ~2s for endpoint resolution, causing 30s+ hangs without real AWS or per-service placebo data5 minutes
- VIRTUAL_ENV not set causes Path(None) TypeError in test_copy_editable_packages before skip check runs2 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- pytest on 6 test suites: 88 passed in 16s (utilities/handler/docs/middleware/async/asgi). 8 core non-AWS tests passed in 0.4s. 2 placebo tests passed in 27s (limited by boto3 endpoint resolution). zappa --version returned 0.62.1.
- Model tokens used
- 768,005
- Exact commit tested
- e9ecb1feea14
- 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.
tests/test_core.py::TestZappa::test_cli_sanity PASSED [ 12%] tests/test_core.py::TestZappa::test_cli_save_python_settings_file succeeded in 27080ms: collected 2 items tests/test_placebo.py .. [100%] ============================== 2 passed in 26.80s ============================== Here's my final report: 2026-10-01T01:17:05.960871Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T01:17:05.960923Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… tokens used 768,005 Here's my final report:
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.5 minutes.
- 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.
- Measured 2 times, so the result is not a one-off.
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.
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 with mocks | 92.00 | 0.27 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.14 |
Topics (from GitHub)
albapi-gatewayawsaws-lambdabottledjangoflaskhacktoberfestlambdapyramidpythonserverlessserverless-frameworkzappa
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zappa)Questions
- Does Zappa run?
- Zappa runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test Zappa?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e9ecb1feea14. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Zappa?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Zappa take to install?
- 1.5 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 Zappa need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Zappa?
- 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.
- Where is the evidence for Zappa?
- 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.