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

@numen-crypto/contract

v0.2.2

Published

Numen API contracts: zod schemas, types, route registry and error codes shared between backend and frontend

Readme

@numen-crypto/contract

Shared API contracts for the Numen platform: zod schemas, inferred TypeScript types, REST route registry and error codes. Consumed by the backend (NestJS) and the frontend (Next.js) so request/response shapes stay in sync from a single source.

Install

Published to npm under the numen-crypto org:

npm install @numen-crypto/contract zod

zod is a peer dependency (the host app provides the single instance).

Usage

import { LoginCommand, ERROR_CODE, REST_API } from '@numen-crypto/contract';

// validate a request body
const body = LoginCommand.RequestSchema.parse(input);

// typed response
const res: LoginCommand.Response = { user };

// route + method metadata
LoginCommand.endpointDetails; // { method: 'POST', path: '/auth/login', summary: '...' }
REST_API.AUTH.LOGIN; // '/auth/login'

Layout

src/
  constants/error-codes.ts   # ErrorCode enum, shared by API error responses
  models/                    # shared zod models (money, pagination, user, session)
  commands/                  # one namespace per endpoint: RequestSchema / ResponseSchema / endpointDetails
    auth/
  api/routes.ts              # flat REST route registry
  index.ts                   # public barrel

Conventions

  • One namespace per command: RequestSchema, ResponseSchema, Request, Response, endpointDetails.
  • Money is always a string (MoneyStringSchema), never a number.
  • zod is a peer dependency — the host app provides the single instance.

Build

npm install
npm run build   # tsup -> dist (esm + cjs + d.ts)