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

@substrat-run/cli

v0.24.14

Published

The substrat CLI — authenticated deploy tooling: push a vertical to the platform, manage its versions and channels

Readme

@substrat-run/cli

The substrat command — authenticated deploy tooling for Substrat. It pushes a vertical to the platform, then manages its versions and release channels.

A vertical is uploaded once and promoted deliberately: push uploads an immutable, content-addressed version; promote binds a channel (e.g. a scope's production pointer) to a version; publish/unpublish control the marketplace catalog. Nothing goes live as a side effect of uploading.

Install

# one-off
pnpm dlx @substrat-run/cli push ./my-vertical

# or add it to a vertical's devDependencies
pnpm add -D @substrat-run/cli

Commands

substrat login                 # authenticate against the control plane
substrat whoami                # show the current identity + reachable tenants
substrat push <dir>            # upload a vertical as a new immutable version
substrat versions <slug>       # list a vertical's uploaded versions
substrat promote <slug> <ver>  # point a channel at a version (the deliberate go-live)
substrat publish <slug>        # list the vertical in the marketplace catalog
substrat unpublish <slug>      # remove it from the catalog
substrat help                  # full usage

Run substrat help for the authoritative flag set — this list is a map, not the spec.

Documentation

https://substrat.net/guide/deploying — authentication, the push/promote model, channels, and the marketplace flow, end to end.

Status

Pre-release (0.x): commands and flags change without notice until the platform GAs.