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

typedhook

v0.2.1

Published

typedhook CLI: pull typed webhook events from the registry, push yours

Readme

typedhook

Typed webhook events without installing the sender's SDK. Senders publish their events to the typedhook registry with the publish action; this CLI pulls them as TypeScript types for @typedhook/verify.

npm install typedhook @typedhook/verify
npx typedhook add acme/billing

This writes typedhook.json, typedhook.lock and src/webhooks/billing.ts, and adds typedhook pull to your postinstall, so the types are regenerated on every install. Commit all three so installs work offline, and keep typedhook in dependencies: the postinstall needs it at install time, so npm ci --omit=dev fails with it in devDependencies.

import { createVerifier } from "@typedhook/verify";
import type { BillingEvents } from "./webhooks/billing";

const verifier = createVerifier(process.env.WEBHOOK_SECRET!);
const result = await verifier.verify<BillingEvents>(req);
if (result.ok && result.payload.event === "invoice.paid") {
  result.payload.data; // typed for invoice.paid
}

Commands

  • typedhook add <owner/name[@range]>... adds registries and generates their types. With no range it pins ^<latest>.
  • typedhook pull only fetches what typedhook.lock pins, and skips the network when the generated files already match it. --update moves to the newest versions the ranges in typedhook.json allow; --check fails when generated files are missing or stale (for CI).
  • typedhook push --events <file> --name <name> --version <semver> publishes your own events from GitHub Actions. Most senders use the publish action instead. Loading a TypeScript events file needs Bun or Node 22.18+.

TYPEDHOOK_REGISTRY_URL overrides the registry URL.