svix-webhooks
The open source and enterprise-ready webhooks service 🦀
Runs with mockssource: GitHubhomepageRustMITcommit cb056ba1a92a
Rust, MIT licensed. The project labels itself: api, background jobs, background tasks, event driven, kafka, message queue, pubsub and queue.
svix-webhooks runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Python client library installs and passes all applicable unit tests (31/31), webhook verification module works end-to-end, CLI tool runs correctly via npx and produces valid signatures.
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 71 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.
- JavaScript library build fails on Node 18: tsdown bundler requires `styleText` from `node:util` which is only available in Node >=212 minutes
- Python test_openapi_json_is_available requires docker-compose which is not installed in this environment1 minute
- JavaScript tests fail: mockttp depends on get-port (ESM-only) but test runner uses require() in CJS mode, Node 18 doesn't support dynamic import for ESM modules in CJS1 minute
- Install time
- 3 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest tests/ in python/ gave 31 passed, 14 skipped (need Svix server), 1 error (needs docker-compose). npx svix-cli version returned 2.6.1. npx svix-cli signature sign produced valid signature.
- Model tokens used
- 509,520
- Exact commit tested
- cb056ba1a92a
- 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_httpretty.py::test_idempotency_key_is_sent_for_create_request
tests/test_httpretty.py::test_client_provided_idempotency_key_is_not_overridden
tests/test_httpretty.py::test_unknown_keys_are_ignored
tests/test_httpretty.py::test_cmg_with_content_default
/tmp/venv/lib/python3.12/site-packages/httpretty/core.py:1077: DeprecationWarning: datetime.datet…
now = datetime.utcnow()
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
======================== 31 passed, 7 warnings in 0.39s ========================
Let me compile the final comprehensive report.
tokens used
509,520
Let me compile the final comprehensive 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 3 minutes, faster than the median of the 9 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.
- 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 10 api projects Argusic has installed and timed, svix-webhooks was the 4th fastest to reach a running state, and 6 of 10 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 | 2/3 | Runs with mocks | 92.00 | 0.13 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.07 |
Topics (from GitHub)
apibackground-jobsbackground-tasksevent-drivenkafkamessage-queuepubsubqueuerabbitmqredisruststreamwebhookwebhook-dispatcherwebhook-ingesterwebhook-serverwebhook-servicewebhookswebhooks-server
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/svix-webhooks)Questions
- Does svix-webhooks run?
- svix-webhooks runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test svix-webhooks?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cb056ba1a92a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test svix-webhooks?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does svix-webhooks 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 svix-webhooks need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing svix-webhooks?
- 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 svix-webhooks compare with the alternatives?
- Of the 10 api projects Argusic has installed and timed, svix-webhooks was the 4th fastest to reach a running state, and 6 of 10 reached one at all.
- Where is the evidence for svix-webhooks?
- 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.