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

@meshwhisper/cli

v0.2.1

Published

MeshWhisper CLI — developer tooling for MeshWhisper projects

Readme

@meshwhisper/cli

Developer tooling for MeshWhisper — the self-hostable, end-to-end encrypted messaging SDK and relay.

npx @meshwhisper/cli init

Commands

init

Scaffolds a MeshWhisper project in the current directory. Asks for your namespace, where your app should connect (Foundation relay for development, self-hosted for production), and what kind of app you're building. Writes:

  • meshwhisper-node/ (self-hosted only) — a complete server deployment: docker-compose.yml, standalone Dockerfiles that install the published @meshwhisper/node and @meshwhisper/push-service packages, a .env (mode 600) with generated Web Push VAPID keys, and a federation-peers.json bootstrapped against the Foundation relay so your node can join the open relay mesh
  • src/meshwhisper.ts (browser/PWA) or meshwhisper-chat.mts (Node.js) — a working SDK skeleton with your namespace and node URL threaded in
  • .gitignore entries for the .env and local identity stores

Idempotent: existing files are never overwritten.

doctor [url]

Health-checks a MeshWhisper node (defaults to the Foundation relay):

npx @meshwhisper/cli doctor wss://relay.myapp.com

Prints the /health snapshot — connected clients, stored blobs, prekey entries, federation status.

vapid

Generates a Web Push VAPID key pair (RFC 8292) with no dependencies — byte-identical output format to web-push generate-vapid-keys:

npx @meshwhisper/cli vapid

Documentation

MIT