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

@baukit/events

v0.3.0

Published

TypeScript half of the Baukit version 1 event envelope: types, Zod schemas, and stable helpers.

Readme

@baukit/events

@baukit/events is the TypeScript half of Baukit's version 1 event envelope. It exports the envelope and ingestion outcome types, Zod schemas, stable validation codes, and validateEventEnvelope for checks that need the authenticated subject and current time.

import { EventEnvelopeSchema, validateEventEnvelope } from '@baukit/events';

const envelope = EventEnvelopeSchema.parse(input);
const code = validateEventEnvelope(envelope, connectionSubject, new Date().toISOString());
if (code !== null) throw new Error(code);

Boundaries

The package does not choose event names or payload fields. Products document and validate those schemas at their own ingestion boundary. Persistence, authorization, delivery, the outbox, and retry policy stay product-owned as well.

What Baukit fixes here is the envelope: the wire fields, the five validation codes, and the seven-day replay boundary. baukit-events is the Rust half of the same contract, and the fixture at fixtures/events/event-envelope-v1.json is what both sides test against, so a change to one without the other fails.