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

@clay-design-system/registry

v0.22.0

Published

The Clay Registry: monday.com's marketing design system as one queryable database (components, sections, tokens, assets, rules) with a zero-dependency query layer.

Readme

@clay-design-system/registry

The Clay Registry: monday.com's marketing design system (components, sections, tokens, assets, rules) as one queryable SQLite database, with a query layer that has no runtime dependencies. Read-only; internal units are not included.

Requires Node >= 22.13 (uses the built-in node:sqlite, no flag needed).

Install

pnpm add @clay-design-system/registry

Use

import { search, get, assetUrl } from '@clay-design-system/registry'

search('hero section')                          // ranked hits: [{ id, kind, name, summary, links, score }, …]
get('section.FeaturesSection')                  // one compact record (import path, story, Figma and CDN links)
get('section.FeaturesSection', { detail: true }) // every column, plus links, relations and renders
assetUrl('asset.icon.calendar')                 // https://… CDN URL

Semantic search (optional)

The database carries one int8 sentence vector per record (embeddings, meta.embedding_model). searchHits(query, { vector }) fuses their cosine ranking with BM25 when you pass the query's embedding; await registry.embed(query) computes it when the optional @clay-design-system/embeddings package is installed (in the working directory or CLAY_EMBED_DIR; it carries the 23 MB MiniLM weights, so nothing is downloaded; CLAY_SEMANTIC=0 disables it). Without a vector, or without that package, search is BM25 exactly as before. The package has no dependencies either way.

const reg = openRegistry()
const vector = await reg.embed('airy breathing room between big blocks on phones') // undefined when semantic search is off
reg.search('airy breathing room between big blocks on phones', { vector })

Also exported: list, related, assetVariants, componentsUsingToken, allowedChildren, pageRecipe, openRegistry, the Registry class, the response types, and DB_PATH (absolute path to the shipped data/clay.sqlite, built when the package is built; gitignored in the repo). The database is the only data file: every record, link and relation is in it.