npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@theoven/webhooks

v0.6.1

Published

Verified inbound webhooks for Oven — Stripe, GitHub, Slack, Svix, Razorpay and Shopify

Readme

@theoven/webhooks

npm

Inbound webhooks that are verified before your handler runs — Stripe, GitHub, Slack, Svix, Razorpay and Shopify.

Part of Oven — the batteries-included framework for Bun.

Install

bun add @theoven/webhooks

Usage

import { stripe, webhook } from '@theoven/webhooks'
import { env } from '@theoven/core'

export default webhook(stripe({ secret: env.string('STRIPE_WEBHOOK_SECRET') }), async (ctx) => {
  // Reached only when the signature verified against the exact bytes that arrived.
  const event = ctx.webhook.payload as { type: string }

  await ctx.queue.dispatch(handleEvent, { event }, { key: ctx.webhook.id })
  return { received: true }
})

The ordering is the whole point, and it is the same argument as auth: true running before a handler: an unverified delivery must be unreachable, not merely inconvenient to act on. A handler that verifies on its first line is one early return away from not verifying.

Providers

| | Header | Signs | Replay-protected | | --- | --- | --- | --- | | stripe | Stripe-Signature | ${timestamp}.${body} | ✓ | | slack | X-Slack-Signature | v0:${timestamp}:${body} | ✓ | | svix | svix-signature | ${id}.${timestamp}.${body} | ✓ | | github | X-Hub-Signature-256 | the body | ✗ | | razorpay | X-Razorpay-Signature | the body | ✗ | | shopify | X-Shopify-Hmac-Sha256 | the body (base64) | ✗ |

svix covers Clerk, Resend, Brex and everything else built on Svix.

Why it uses the raw body

A signature covers the exact bytes. Re-serialising a parsed body produces different ones — a reordered key, a changed number format — and a signature that fails for reasons no amount of staring at the JSON explains. This reads ctx.rawBody, which core keeps for precisely this.

Limitations

  • Three providers cannot detect a replay. GitHub, Razorpay and Shopify sign only the body, so a captured delivery is valid forever. verifier.replayProtected says so; deduplicate on ctx.webhook.id if it matters.
  • No delivery log. Idempotency is yours — the queue's dedup keys are the usual answer.
  • JSON bodies only for ctx.webhook.payload. ctx.webhook.raw is always there for the rest.

Documentation

https://theoven.app/docs/bricks/webhooks/

License

MIT