mangum

AWS Lambda support for ASGI applications

Runs with mockssource: GitHubhomepagePythonMITcommit f2adb550c778

Python, MIT licensed. The project labels itself: api gateway, asgi, asyncio, aws, aws lambda, django, fastapi and lambda.

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

Mangum 0.22.0 installed in Python 3.12.3 venv; 106/110 unit/handler/protocol tests pass; 4 Docker-dependent integration tests skipped; adapter correctly processes ASGI apps through API Gateway, HTTP Gateway, ALB, and Lambda@Edge handlers.

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

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
2
last tested
stars
2,139
forks
135
open issues
39
watchers
16
size
3 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 mangum, 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.

  • Python environment is externally managed (PEP 668), requiring venv1 minute
  • pip install mangum[dev] failed: dev extra not defined1 minute
  • boto3 and testcontainers not installed from dev extras1 minute
  • Docker not available: localstack fixtures crash test run1 minute
Install time
3 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
pytest tests/ -q --tb=no -k 'not real_lambda' returned '106 passed, 4 deselected in 0.34s'; smoke test with synthetic API Gateway event returned status=200, body='Hello from Mangum!'
Model tokens used
67,443
Exact commit tested
f2adb550c778
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.

  4. Docker unavailable → patched `tests/conftest.py` to skip Docker-dependent fixtures gracefully
- **106 of 110 tests pass.** 4 Docker/localstack integration tests skip with "Docker is not availab…
tokens used
67,443
**Summary:**
- Created a venv (`/tmp/mangum-venv`) and installed Mangum and all dev/test dependencies successful…
- Discovered 4 blocking errors, all fixed:
  1. Externally-managed Python system (PEP 668) → used venv
  2. `[dev]` extra not defined in pyproject.toml → installed dev deps manually
  3. `boto3`/`testcontainers` missing → installed separately
  4. Docker unavailable → patched `tests/conftest.py` to skip Docker-dependent fixtures gracefully
- **106 of 110 tests pass.** 4 Docker/localstack integration tests skip with "Docker is not availab…

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 7 comparable projects Argusic has measured.
  • Recovered from all 4 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.

Of the 8 api-gateway projects Argusic has installed and timed, mangum was the 2nd fastest to reach a running state, and 4 of 8 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 Runner2/3Runs with mocks92.000.03
Argusic Runner1/3Did not run20.000.02

Topics (from GitHub)

api-gatewayasgiasyncioawsaws-lambdadjangofastapilambdapythonpython3quartsanicserverlessstarlette

Embed the badge

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

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

Questions

Does mangum run?
mangum runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test mangum?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f2adb550c778. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test mangum?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does mangum 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 mangum need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mangum?
4 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 mangum compare with the alternatives?
Of the 8 api-gateway projects Argusic has installed and timed, mangum was the 2nd fastest to reach a running state, and 4 of 8 reached one at all.
Where is the evidence for mangum?
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.

Discussion