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

@quireco/cli

v0.2.0

Published

Triage and investigation CLI for Quire.

Readme

Quire CLI

Quire verifies software the way a careful QA engineer would. Give it a bug report, a pull request to check, or a flow to test; it drives the product, records evidence, and hands back a clear verdict (reproduced, not reproduced, passed, failed, or blocked) with screenshots, recordings, and the steps it took.

Install

npm install --global @quireco/cli

Requires Node.js 24 or later, and Chrome or Chromium for browser runs.

Set up

The easiest setup is to ask the coding agent in your repository:

Help me set up Quire for this project. Follow https://skills.quire.sh/setup.

It installs the CLI, signs you in, writes .quire/runbook.md (how Quire should reach and safely use your app), and runs a smoke check. To do it by hand:

quire login     # sign in through your browser
quire doctor    # check sign-in, model access, and runbook

For CI or remote agents, set QUIRE_API_TOKEN (Settings → Access token) instead of quire login.

Run

quire run "Reproduce: editing a todo's title doesn't survive a reload" --url http://localhost:3000
cat issue.md | quire run --url https://staging.example.com
quire "Verify checkout before I approve this PR"

Quire works against an app that is already running; it never starts, migrates, or seeds it. Pass the URL with --url or QUIRE_WEB_URL. The run streams its progress and ends with a handoff; open the run link to see the full evidence in Quire.

Commands

| Command | What it does | | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | quire run [prompt] | Start a run. Reads a piped brief from stdin. Same as quire "<prompt>". | | quire runs | List recent runs (--all for every project). | | quire status <run> | Show a run's current status. | | quire watch <run> | Follow a run's live progress. | | quire cancel <run> | Stop a running run (--force to kill it). | | quire sync <run> | Retry uploading a finished run's evidence. | | quire doctor | Diagnose setup (--strict fails on warnings too). | | quire login / logout | Sign this machine in or out. | | quire whoami | Show the signed-in account and model source. | | quire test-accounts <list\|show\|add\|update\|remove> | Manage test-account logins Quire may use for your app. | | quire agent install --harness <name> | Add Quire support for a coding agent: amp, claude, codex, cursor, opencode, or pi. | | quire update | Update the CLI (--check to only compare versions). |

quire run options

| Option | Effect | | ------------- | ----------------------------------------------------------------------------- | | --url <url> | The running app to verify. | | --detach | Start in the background and print the controls instead of following the run. | | --headed | Show the browser window. | | --sandbox | Run your pushed GitHub commit in a remote sandbox instead of on this machine. | | --json | Print the run handle as JSON (for scripts and agents). |

Most commands accept --json; quire <command> --help lists every option.

Test accounts

For flows that need a login, register an account once; Quire signs in with it during runs and never writes the password to run artifacts.

quire test-accounts add --label "Staging admin" \
  --login-url https://staging.example.com/login --email [email protected]

add prompts for the password (or use --password-stdin). Passwords are never accepted as arguments.

Environment

| Variable | Purpose | | ----------------- | --------------------------------------------------------------------- | | QUIRE_API_TOKEN | Access token for CI and remote agents, used instead of quire login. | | QUIRE_WEB_URL | Default target URL when --url isn't given. | | QUIRE_RUNS_DIR | Where runs are stored (default ~/.local/share/quire/runs). |

Learn more

  • Manual: https://quire.sh/manual
  • Runs and evidence: https://quire.sh/runs