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

@slurry/cli

v0.11.0

Published

Slurry from the command line: simulations, request checks and test suites for coding agents and CI

Readme

slurry CLI

Slurry from the command line: create simulations of real vendor APIs, check the calls your system made, and run test suites in CI. Built for coding agents first: every command takes --json, exit codes are stable, and slurry guide prints a skill file an agent can load.

Node 20 or later. One file, no runtime dependencies.

npm install -g @slurry/cli    # then: slurry help
npx @slurry/cli help          # or without installing

Sign in

slurry login                     # approve a code in the browser; the key is saved for this machine
export SLURRY_KEY=slurry_acct_...   # or, in CI, an account key from slurry.io/app/keys

A saved key is only ever sent to the API that issued it. SLURRY_API points the CLI at another engine (https, or http on localhost).

The loop

slurry sims create --from jira --name "Acme Jira" --wait --write-env .env
slurry requests verify acme-jira --method POST --path /rest/api/3/issue --times 1
slurry test billing --speed 60 --junit slurry-results.xml

--write-env appends ACME_JIRA_BASE_URL and ACME_JIRA_API_KEY to the file instead of printing the key, so it never lands in a log. requests verify exits 1 with the near misses (the filter each one failed). test exits 0 only if the run passed, and aborts the run at --timeout (default 30m).

In CI

- name: Slurry tests
  env:
    SLURRY_KEY: ${{ secrets.SLURRY_ACCOUNT_KEY }}
  run: npx @slurry/cli test billing --speed 60 --junit slurry-results.xml

Runs started with the CI variable set are tagged ci.

Commands

slurry help lists them all; slurry <command> --help shows options. Groups: login, whoami, library, sims, records, requests, state, eval, snapshots, forks, scenarios, actions, rules, webhooks, keys, suites, cases, test, runs, api (any endpoint), guide, agent (puts Slurry into Claude Code and Cursor).

Exit codes: 0 ok, 1 a check failed, 2 usage, 3 not signed in or not allowed, 4 not found, 5 API or network.

Developing

From the repo: pnpm --filter @slurry/cli slurry <args> runs the source; pnpm --filter @slurry/cli build writes dist/slurry.mjs; pnpm --filter @slurry/cli test.