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

@block-smith/cli

v0.1.0

Published

BlockSmith CLI — log in, scan a repo, pull promoted design rules, and wire up Cursor MCP.

Readme

@block-smith/cli

Command-line tool for BlockSmith — promote design in the wiki, then pull governed rules and wire up Cursor MCP from your terminal.

Self-contained: one global install, no peer packages to manage.

Install

npm install -g @block-smith/cli

Requires Node.js ≥ 18.

Quick start

# 1. Create an API key in the wiki: Sync → API keys
blocksmith login --key bs_live_… --url https://blocksmith-mocha.vercel.app

# 2. Pull the rules you promoted into your repo (writes DESIGN.md + .blocksmith/)
blocksmith pull --doc upload:scan-your-kit.md

# 3. Point Cursor at the remote MCP (pinned, promoted blocks only)
blocksmith mcp-url

Commands

| Command | What it does | |---------|--------------| | login --key <bs_live_…> [--url <host>] | Verify and save your API key (--url defaults to the hosted SaaS). | | whoami | Show the account the key belongs to. | | scan [path] | Scan a local repo and upload it to the server. | | scan --fixture vendor | Scan the demo vendor on the server. | | scan --github <org/repo> | Scan a public GitHub repo on the server. | | pull --doc <ref> [--workspace <path>] | Pull promoted rules into DESIGN.md (auto-detects the git repo). | | codegen [--doc <ref>] | Generate @blocksmith/<slug> from a scan (Pulse, early). | | mcp-url | Print the remote MCP URL for Cursor. | | --version, --help | Version / usage. |

Config is stored at ~/.blocksmith/config.json.

blocksmith scan <localPath> needs the BlockSmith scan engine on the machine (clone the repo and set BLOCKSMITH_ROOT). For a zero-setup scan use --github or --fixture, which run on the server.

Develop / build

# from the monorepo root
npm run build -w @block-smith/cli      # bundles src + SDK into dist/cli.js
node packages/cli/dist/cli.js --help

The build (build.mjs) bundles the workspace @blocksmith/sdk straight from source with esbuild, so the published artifact is a single dependency-free file.

Publish (maintainers)

npm login                              # one time
npm publish -w @block-smith/cli         # prepublishOnly rebuilds the bundle

@blocksmith/sdk does not need to be published — it is bundled in.