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

cerato

v0.0.5

Published

End-to-end typesafe API definitions for TypeScript

Readme

cerato

[!CAUTION] Extracted from a toy project — extremely unfinished, lightly tested, limited, experimental code.

Note for AI Agents: there's a docs folder published with this package; read the docs for help using the library.

The core of Cerato, an experiment in making it easy to build end-to-end typesafe APIs in TypeScript. You describe an API once as a plain value, and interpret that description into different targets — a typesafe fetch client, a Hono server — via adapter packages.

This package holds the API definition primitives (Endpoint, mapApi) and the types that flow through every adapter. It has no runtime dependencies; Zod is a peer dependency, used to validate anything coming "in" at runtime.

Install

pnpm add cerato zod

Then add whichever adapters you need:

Defining an API

import { Endpoint } from "cerato";
import z from "zod";

export const api = {
  ping: Endpoint.get().output(200, z.object({ ok: z.boolean() })),
  createTask: Endpoint.post()
    .input(z.object({ title: z.string() }))
    .output(201, z.object({ id: z.string() })),
};

api is just a value. On its own it does nothing — hand it to an adapter to get a client or a server. Both derive their types from this single definition, so the client and server stay in lockstep with the schema.

Entry points

  • cerato — the curated, public API surface (Endpoint, mapApi, and the types you need to describe and consume APIs).
  • cerato/internal — the shared building blocks the official adapters are built on. Not covered by semver for external consumers; you shouldn't need to import from it unless you're writing your own adapter.

Versioning note for adapters

Adapters take cerato as a peer dependency so a consumer resolves a single shared copy. This matters at runtime: the adapters use instanceof against core's Endpoint/Multi classes, and two copies of core in one dependency tree would silently fail to recognise each other's endpoints.