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

@app-studio/qa-cli

v0.5.0

Published

The qa command: the layered run, the doctor, adoption, hardened end-to-end orchestration, seeding and the ratchets.

Readme

@app-studio/qa-cli

One command surface for humans and agents.

qa state validate
qa state list
qa state inspect --id <id>
qa state run --id <id> [--mode mock|live]

qa design record --file <acceptance.json> --reviewer <designer-id>
qa design validate [--feature <key>]
qa design list

qa scenario validate
qa scenario list
qa scenario coverage
qa scenario run --id <id> [--mode mock|live] [--engine <name>] [--profile fast|proof|record]
qa scenario run [--mode mock|live] # complete release-candidate portfolio
qa scenario benchmark --id <id> [--engines chromium,lightpanda] [--runs 5]

Validation reads the canonical artifacts. Runtime commands resolve the host command from qa.bindings.json and pass the selected ID through environment variables. Named engines select application-owned commands; capability declarations stop a DOM-only engine from being used for visual proof or video. fast emits a verdict without checkpoint media, proof is the default release evidence, and record enables video-oriented diagnostics. The CLI does not maintain a copied catalogue or a second browser implementation.

Use qa run --list to inspect the progressive proof layers and qa run --from <layer> only after lower layers are known green.