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

spoke-code

v0.2.0

Published

Install and update the spoke-code kit with your subscription license key.

Readme

spoke-code

The command line for the spoke-code kit. Your subscription comes with a license key; this tool turns it into a site folder and keeps that folder up to date.

npx spoke-code create my-site     # new site from the current release
npx spoke-code create my-site --theme spoke   # the same, starting from a theme
npx spoke-code update             # merge the newest release into this site
npx spoke-code status             # which version, which seat
npx spoke-code logout             # free this machine's seat

create asks for your license key once and stores it in your user config folder. A seat is one machine; logout frees it, and the Polar customer portal shows every active seat.

Without --theme you get the blank starter. With one, that theme becomes your site's apps/web, and update keeps bringing you that theme's changes.

Updates use git: the pristine kit lives on a hidden spoke-code/upstream branch, and update merges the new version into your branch. Your changes stay; where the two collide, git leaves a conflict for you or your assistant to resolve. Started from a zip instead? npx spoke-code adopt sets that branch up for the version you have. A site made before the project was renamed (it has a .vibe-check folder) is moved to the new layout the first time you run update or adopt; commit your work first.

Nothing in the kit itself calls home. Only create, update, and adopt check the key.