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

@tolt/cli

v0.1.0

Published

The Tolt command line: stream your webhooks to localhost, trigger sample events, and talk to the API from your terminal.

Readme

@tolt/cli

The Tolt command line. Stream your webhooks to localhost while you build, fire sample events, and talk to the API from your terminal.

Install

npm install -g @tolt/cli

Or run it without installing:

npx @tolt/cli listen --forward-to http://localhost:3000/api/webhooks/tolt

Get started

Log in once with an API key from your Tolt dashboard (Settings → API):

tolt login

Then point your webhooks at your local server:

tolt listen --forward-to http://localhost:3000/api/webhooks/tolt

listen prints a signing secret. Configure your local webhook handler to verify with it, and every event Tolt sends for your org is delivered straight to your machine, with the original signature intact. In another terminal, send a sample event to see it flow through:

tolt trigger commission.created

Commands

| Command | What it does | | --- | --- | | tolt login | Verify an API key and store it. | | tolt whoami | Show the active profile and confirm the key still works. | | tolt logout | Remove the stored key for a profile. | | tolt listen | Stream your webhooks to a local URL. --forward-to <url>, --events a,b. | | tolt trigger <event> | Send a sample event of that type through your webhooks. |

Configuration

The CLI resolves your API key in this order:

  1. --token <key>
  2. TOLT_API_KEY
  3. the active profile in ~/.config/tolt/config.json

Use --profile <name> to keep more than one account, and --api-url <url> (or TOLT_API_URL) to point at a non-production environment.

Output

Every command prints human-readable text on a terminal and JSON when piped. Force either with --json / --human, or set TOLT_JSON=true. In JSON mode an error is exactly {"error":"message"} on stdout with exit code 1.