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

sz.ws

v0.1.3

Published

Official CLI for the sz.ws studio — terminal lobby, and entrypoint for the ecosystem.

Readme

sz.ws

Official CLI for the sz.ws studio.

npx sz.ws

Bare run opens an interactive terminal lobby (in a TTY): coloured ASCII mark in a centered card, ↑↓ to select, ↵ to open. Piped / CI falls back to a static catalogue. No account, no network.

| Key | Action | |---|---| | / k j | Move selection | | | Open the focused product | | o | Open https://sz.ws | | q | Quit |

Force the static print: SZ_WS_STATIC=1 npx sz.ws.

Product catalogue

The list is bundled with the CLI, and the interactive lobby additionally tries https://sz.ws/api/catalogue.json so a new product can appear without a release. If that fetch fails, times out, or returns anything malformed, it is ignored silently and the bundled list is what you see — the endpoint is an enhancement, never a dependency.

| Var | Meaning | |---|---| | SZ_WS_CATALOGUE_URL | Override the endpoint | | SZ_WS_OFFLINE=1 | Never fetch (implied by CI=true) | | SZ_WS_CATALOGUE_CACHE | Override the cache path |

Responses are cached for 6h under ~/.config/sz.ws/catalogue.json. Only the interactive lobby fetches; piped and SZ_WS_STATIC=1 runs read cache or fall back, so scripts never wait on the network.

Every entry's href must be https on an sz.ws host. Enter opens that URL in a browser, so a remote list is remote control over where the CLI sends people; entries failing the check are dropped. The response shape:

[{ "name": "drop", "status": "live", "note": "ephemeral hosting",
   "accent": "#FF5310", "href": "https://drop.sz.ws" }]

Install

npm install -g sz.ws
# or
npx sz.ws

Commands

| Command | Description | |---|---| | sz.ws | Interactive lobby (default) | | sz.ws <product> … | Run a studio product — routed to @sz.ws/<product> via npx | | sz.ws open [path] | Open sz.ws (or a subpath) in the browser | | sz.ws install <pkg> | Install @sz-ws/<pkg> | | sz.ws init | Scaffold (stub) | | sz.ws login / whoami | Auth stubs | | sz.ws version | Print version | | sz.ws help | Usage |

Routing

Anything that is not a built-in command is treated as a product name and handed to @sz.ws/<name> with the rest of the arguments untouched:

npx sz.ws drop ./site.zip 7d    # → npx -y @sz.ws/drop ./site.zip 7d

This is a wildcard, not a table of known products: a table would need editing and republishing every time the studio ships something. npm is already the registry of what exists — if the package is there it runs, and if it is not you get told so. stdio is inherited, so the child owns the terminal and its own progress bars and prompts work normally.

Design notes

  • Mark colours follow the brand loop S·Z·W·S — yellow / green / blue / pink.
  • The lobby is a single boxed card, horizontally centered in the terminal.
  • NO_COLOR=1 (or a non-TTY pipe) prints a plain lobby.
  • Narrow terminals (< 54 cols) collapse the figlet to a compact sz.ws wordmark.

Requirements

  • Node.js >= 18

Links

License

MIT