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

@qa-ai-stlc/cli

v0.10.0

Published

The qa command: init, doctor and every deterministic engine operation exposed for CI and humans.

Readme

@qa-ai-stlc/cli

The qa command: a thin client over @qa-ai-stlc/core and @qa-ai-stlc/explorer for CI and humans. qa init creates the .qa/ store and runs the testing scope survey; qa doctor checks Node, browsers, identities and environment reachability before a run; qa explore crawls the configured environment, optionally merges static source analysis (--static) and pick-mode entries (--pick <url>), and writes the selector registry and a generated locator module; qa explore --verify re-checks stored selectors against the live page without re-crawling. qa config set testing.<type> <value> changes a scope decision after init; qa config add environment <name> --base-url <url> --allowlist <a,b,c> and qa config add identity <name> --auth <cdp-attach|storage-state> --secret <QA_...> [--login-url <url>] [--username <user>] add a schema-validated entry instead of hand-editing config.yaml. qa scope --from file --path <path> or qa scope --from text --content <text> --label <label> extracts requirements (one per level-2 Markdown heading) into artifacts/scope.json, upserting by requirement id on a repeated call. qa cases add --path <path> validates a test case written as JSON — it must link to at least one requirement, and every linked id must actually exist in artifacts/scope.json — and registers it under artifacts/cases/<id>.json. qa cases render <id> renders a registered test case as a numbered Markdown document (metadata, preconditions, steps, expected result), so it can be handed to a stakeholder instead of raw JSON. qa approve <gate> --artifact <path> --approved-by <name> [--note <text>] hash-binds an approval to a pipeline gate (scope, cases, approved in order); qa validate recomputes every gate's status from the approval ledger and re-checks every registered case's requirement links, exiting non-zero for a reopened gate or an unlinked case. Every command supports --json for machine-readable output and exits non-zero on failure.

Part of QA-AI-STLC. See the repository root for license, contributing and security information.