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

@metacoding.io/regulator-control-room

v0.1.3

Published

The maintainer's read-only control room: one page over the `regulator status` read model — definition topology, running instances, and what each unit is doing.

Readme

@metacoding.io/regulator-control-room

The maintainer's control room: one read-only page over the regulator status read model (packages/regulator). It answers three questions and owns no state:

  • Definition — the registry as a topology (S5 → S1 columns, one card per regulator, the channels each record declares it consumes and emits) and the workloads.
  • Instances — every instance's units, leases and unrouted signals.
  • Inspector — the whole record for a regulator or a unit (contract, result report, attempts): the record, not a summary of it.
pnpm build
node packages/control-room/dist/cli.js --definition packages/regulator --instance /path/to/repo [--instance ...] [--port 4321]

Then open http://127.0.0.1:4321/. The page refreshes every five seconds; #reg=<id> and #unit=<instance index>/<unit id> deep-link the inspector. Every non-GET request is refused with 405 — the moment this grows a button that changes anything it has become an authority surface, and it will not (the rule is from the archived CONTROL-REGISTRY.md §6).

Nothing here reads the repository: units come from the execution store, leases from the lease store, signals from the signal sink, regulators from the registry files.