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

@notato/schema

v0.2.0

Published

The wire format every Notato SDK and server share: Zod schemas for annotations and bundles, and schema.json made from them.

Readme

@notato/schema

The wire format of Notato: what an annotation and a bundle of annotations look like, shared by every SDK, the server and the board. It is the one contract between them, so a change here is a change for every platform.

import { Annotation, Bundle, SCHEMA_VERSION } from "@notato/schema";

const note = Annotation.parse(JSON.parse(body)); // throws on anything malformed
  • Zod schemas and their types: Annotation, Bundle, Reply, ElementIdentity, AssetRef, Environment, Target, Variants, and the enumerations Mode, Severity, Intent and Status. Each is both a schema (Annotation.parse) and a type (Annotation). The comments in src/index.ts say what each field means.
  • SCHEMA_VERSION: bundles carry it, so an importer can refuse one it does not understand.
  • schema.json (@notato/schema/schema.json): the same definitions as JSON Schema, for languages without Zod (the .NET SDK's contract test reads it; the other native SDKs run what they write through the Zod schemas, as sdks/README.md describes). It is generated: after changing src/index.ts, run bun run build:schema from the repository root.
  • sampleAnnotation and sampleBundle: fully populated examples, for tests and for the samples Notato sends.

Read leniently: ignore fields you do not know, and keep enumerations as strings, so a newer server never breaks an older app. A change that an older reader would reject needs a new SCHEMA_VERSION.