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

@zwaggen/cli

v0.2.2

Published

Zwaggen CI CLI — batch run + diff API specs (zwag)

Readme

@zwaggen/cli (zwag)

CI CLI for Zwaggen specs.

Install (workspace)

This is a workspace-internal package; build with:

pnpm --filter @zwaggen/cli build

Commands

zwag diff <base.json> <current.json>

Diffs two Zwaggen spec files. Prints breaking + non-breaking changes. Exit 1 if any breaking change is present, 0 otherwise.

zwag run <spec.json> [--base-url <url>] [--filter <regex>]

Runs every endpoint in the spec against spec.info.baseUrl (or --base-url if given). Smoke test: path params are substituted with the literal string "1", no body is sent, no authentication is wired (see Limitations below). Reports PASS/FAIL per endpoint. Exit 1 if any endpoint fails.

--filter takes a regex; only endpoints whose METHOD /path matches are run (e.g. --filter '^GET /users').

An endpoint passes iff the request completes without a network error and every assertion attached to the endpoint passes. With no assertions, any successful HTTP response (including 4xx/5xx) counts as PASS; add assertions.expectedStatus in the spec to gate on status.

Exit codes

  • 0: success
  • 1: failures found (broken endpoints for run; breaking changes for diff)
  • 2: CLI misuse (missing file, bad JSON, no base URL, etc.)

Limitations (v0.1.0)

  • No authentication. Endpoints that require auth will return 401/403 and FAIL (or PASS silently if no expectedStatus assertion is set).
  • Path params are hard-coded to "1". Endpoints requiring real IDs will 404.
  • Request bodies are not sent.
  • Sequential execution only.
  • Text output only (no --json).

Follow-ups are tracked in docs/TODO.md under "Follow-up from shipped work".