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

@bridgething/catalog

v0.17.0

Published

The catalog.v1 schema, validator and resolution rules for the bridgething webapp store. Use it to publish a source or to write a client that reads one.

Readme

@bridgething/catalog

The catalog.v1 schema, its validator, and the rules for resolving what to install. A catalog is the document a bridgething app source publishes; the companion apps, the desktop app, and bridgething.com all read one through this package.

bun add @bridgething/catalog
import { newestCompatible, validate } from '@bridgething/catalog';

const catalog = validate(await (await fetch(url)).json());
const version = newestCompatible(catalog.apps[0], deviceLibVersion);

validate checks the JSON Schema and then the cross-reference rules the schema cannot express: app ids are unique uuidv7, a version appears once per app, versions[] is newest-first by released_at, extension permissions are real Deno descriptors, and an app shipping a native extension names a github.com repo as its source. It throws CatalogValidationError listing every failure, not the first. validateSchema and validateInvariants are exported separately.

newestCompatible sorts by released_at itself and compares min_libbridgething_version against the version the device reports, leading v and all. Do not pre-sort or pre-strip.

An installed app takes updates only from the source it came from. A different source offering the same app id is a cross-grade the user picks deliberately, never a silent update.

Publishing a source: bun create bridgething scaffolds one, and @bridgething/source is the toolkit it wires up, which builds, hosts and validates for you. Hosting your own means serving Access-Control-Allow-Origin: * on the catalog and every download.url, and never changing the bytes behind a published version. The schema ships here as @bridgething/catalog/schema.v1.json.