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

@assemora/schema

v0.2.6

Published

Schema primitives: field definitions, type inference, neutral JSON representation

Readme

@assemora/schema

Schema primitives: field definitions, type inference, neutral JSON representation.

Implementation phase: 1 — implemented.

One declaration is at once a runtime parser, a compile-time type and a JSON Schema description, so validation, the database, Studio forms, OpenAPI, the SDK and MCP all read a single source (SPEC.md §3.4, §42).

import { enumOf, number, object, string, uuid, type Infer } from '@assemora/schema'

const Article = object({
  id: uuid(),
  title: string().min(2),
  status: enumOf('draft', 'published'),
  views: number().optional(),
})

type Article = Infer<typeof Article>
// { id: string; title: string; status: 'draft' | 'published'; views?: number }

const result = Article.parse(payload)
if (!result.ok) result.issues // [{ path: ['title'], code: 'min', message: '...' }]

Parsing never throws — the caller decides what a failure means. Keys outside the declared shape are dropped rather than passed through, which is how mass assignment is prevented (SPEC.md §85).

Workspace dependencies

none, and there never will be any. pnpm boundaries enforces it: every layer and every browser bundle reads this package.