Analysis updated 2026-05-18
Test a webhook handler locally by sending realistic, correctly signed sample events.
Replay a captured webhook delivery after fixing a bug, without asking the provider to resend it.
Verify that a captured delivery's signature matches your app's signing secret.
Inspect the full history of webhook requests your app received, stored in a local SQLite file.
| arino08/hookline | abc3dz/mixxx | abyo-software/ferro-stash | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Rust | Rust | Rust |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 2/5 | 4/5 |
| Audience | developer | general | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires a Rust toolchain to install via cargo, no accounts or external services needed to start.
hookline is a command line tool that helps developers catch, inspect, replay and fake webhooks while building and testing webhook handlers on their own machine. It runs a small local server that logs every incoming request into a SQLite file and can optionally forward each one to your real application. From that saved history you can look at any request in detail, send it again, or check that its signature is valid, all without needing an internet tunnel, a provider account, or any hosted service. If you have used Stripe's own local listening tool before, hookline offers that same kind of workflow but for many different providers at once. The basic loop is simple. You start the capture server with hookline listen, then either wait for real webhooks to arrive or use hookline trigger to send yourself a realistic, correctly signed sample event from a provider like GitHub, Stripe or Razorpay. From there hookline ls and hookline show let you browse and inspect what was captured, hookline verify checks a captured delivery's signature against your own secret, and hookline replay resends a stored delivery so you can rerun your handler after a fix without bothering the original provider again. Under the hood, hookline understands the exact signature scheme each provider uses, including GitHub's HMAC based header, Stripe's timestamped signature, Razorpay, Slack and Shopify's own formats, and can both generate and check them correctly. Supported providers are recognized automatically from their request headers and labeled accordingly, while requests from unrecognized senders are still captured normally. Since hookline only listens on your own machine and does not include a built in tunnel, reaching it from the public internet requires pairing it with a separate tool like ngrok or Cloudflare Tunnel. Installation is done with a single cargo install command, since hookline is written in Rust, or by cloning the source and building it yourself. All captured data lives in one local SQLite database file, so it can be queried directly, backed up, or simply deleted to clear history. The project is released under a dual MIT or Apache 2.0 license.
A local command line tool that captures, inspects, replays and fakes signed webhooks for testing your own app without a tunnel.
Mainly Rust. The stack also includes Rust, SQLite, CLI.
Free to use, modify and redistribute for any purpose, including commercial use, under either the MIT or Apache 2.0 license.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.