All 112 Dependencies
Every package Svix depends on, ranked by repo health score.
Svix is a webhooks-as-a-service platform, and svix-webhooks is the fully open source, self-hostable version of the exact same Rust server that powers Svix's own commercial cloud offering. Instead of every SaaS company reinventing outbound webhook delivery — retries, HMAC signing, endpoint management, delivery logs — teams can run svix-server themselves or use official SDKs to talk to a hosted instance, with no functional gap between the two.
The repository is a large monorepo centered on svix-server, an axum-based Rust API backed by PostgreSQL (via sea-orm) and a pluggable message queue (Redis, Redis Cluster/Sentinel, or RabbitMQ through the omniqueue crate). A dedicated async worker drives delivery attempts with jittered exponential backoff, disables endpoints after repeated failures, and reports status through operational webhooks. Around the server sit svix-bridge, an agent that wires Kafka or other queues directly to webhook delivery or ingestion without a custom receiver, and svix-cli, an npm-distributed CLI for scripting the API.
On the client side, Svix maintains eight officially supported SDKs (Go, Python, TypeScript/JavaScript, Java, Kotlin, Ruby, C#, PHP) plus a native Rust crate and a Terraform provider, all generated from a shared OpenAPI schema via the codegen pipeline. Every SDK ships the same signature-verification logic, implementing the vendor-neutral Standard Webhooks specification that Svix helped create — so the same verification code can validate webhooks from any Standard Webhooks-compliant sender, not just Svix.
The project is MIT licensed with no enterprise fork or feature gating: there's no `ee/`, `enterprise/`, or `pro/` directory, and no license-check gating found in the server source, so everything in the self-hosted build is available with no license key required.