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

supernova-ai

v0.1.0

Published

Short, sortable, prefixed IDs (org_0slcSpOdnti) backed by the Web Crypto CSPRNG. Zero dependencies.

Readme

supernova-ai

Short, sortable, prefixed identifiers — the ID scheme we use across Supernova. Zero dependencies.

import { generateId } from "supernova-ai";

generateId("org"); // → "org_0slcSpOdnti"
generateId("app"); // → "app_0slcSsdWhkY"

Each ID is a prefix, a fixed-width base62 timestamp (milliseconds since 2025-01-01), and a few random characters. That gives you three things a UUID doesn't:

  • Readable. The prefix tells you what the ID points at, in a log line or a URL, without looking it up.
  • Sortable. The timestamp leads and is fixed-width over an ASCII-ordered alphabet, so plain lexicographic order — sort, order by, a B-tree — is creation order to the millisecond. Inserts stay at the right edge of the index instead of scattering through it.
  • Short. 15 characters for a 3-character prefix, against 36 for a UUID.

API

generateId(prefix, options?)

  • randomness — number of random characters appended after the timestamp. Default 4.
  • separator — default "_".

The return type is templated, so generateId("org") is typed as `org_${string}` and survives being passed around as a branded ID.

randomString(length, alphabet?)

A cryptographically secure random string, rejection-sampled to avoid modulo bias. Suitable for tokens and secrets — a length-n string over the default 62-character alphabet carries n * log2(62) ≈ 5.95n bits of entropy.

Choosing randomness

IDs are unique by timestamp plus randomness. They are not coordinated across processes, so uniqueness is a birthday problem within a single millisecond: k IDs minted in the same millisecond over a space of 62^randomness collide with probability about k² / (2 · 62^randomness).

The default of 4 characters (14.8M) is sized for the case where a millisecond holds a handful of IDs, which is what request-driven code actually does. Minting in a tight loop is where it runs out — measured on one core:

| randomness | space | collisions per 200k minted at ~200 ids/ms | | --- | --- | --- | | 4 (default) | 1.5e7 | a few | | 6 | 5.7e10 | none observed | | 8 | 2.2e14 | none observed |

So: leave it at 4 for records created by requests, jobs, and users. Raise it to 6 or 8 when a loop mints IDs continuously, or when many machines mint against the same prefix at once. It costs one character each.

Notes

Randomness comes from Web Crypto crypto.getRandomValues, a global in Node 18+, Deno, Bun, Cloudflare Workers, and browsers. Math.random() is never used.

The 7-character timestamp is fixed-width deliberately: a variable-width encoding stops sorting the moment it gains a character. 7 base62 characters carry the clock to the year 2136.

License

MIT