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

@operatorgrade/cli

v0.1.1

Published

Operator-Grade design system CLI: agent cheat sheet, component/token/doc lookup, and the zero-hardcoded-values check.

Readme

@operatorgrade/cli

Scriptable lookup for the Operator-Grade design system, built for AI agents and CI. The published package reads baked JSON only — no component source, no build step, no runtime dependencies.

Install & reliable invocation

npm i -D @operatorgrade/cli

Add a script so agents and CI invoke it deterministically (no PATH guessing):

"scripts": {
  "operator": "node node_modules/@operatorgrade/cli/bin/operator.mjs"
}

Commands

| Command | Behavior | | --- | --- | | operator init [--all] | Write the AGENTS.md + CLAUDE.md agent cheat sheet (non-interactive, idempotent; --all adds theming + page-building pointers). | | operator component [Name] | List components, or print one's props, intents/sizes, import, do/don't. | | operator tokens [group] | List token groups, or print tokens with resolved Day / Night-NVG / Mono values — e.g. operator tokens semantic.color.threat. | | operator docs [topic] | List doc topics or print one (getting-started, theme-as-mode, standards, …). | | operator template [--list \| <name>] | List @operatorgrade/templates page templates, or print one's usage. | | operator check | Run the zero-hardcoded-values token gate; exits non-zero on a raw value. |

For a live agent connection

operator init gives the buyer's agent a file; @operatorgrade/mcp exposes the same catalog/tokens/docs over the Model Context Protocol for a live connection.

Development (this monorepo)

data/*.json is baked from the component source, token JSON, and docs by npm run build:data -w @operatorgrade/cli (also runs on prepublishOnly). npm test -w @operatorgrade/cli includes a drift check: if source changed without a rebake, it fails.