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

humanqa

v0.1.4

Published

Evidence-first product quality checks for web apps

Readme

HumanQA CLI

Evidence-first product quality checks for web applications.

HumanQA runs a declared, safe browser journey and turns the observed state into screenshots, a Playwright trace, deterministic findings, transparent release risk, portable reports, and a reviewed regression-test scaffold.

Install

npm install --global humanqa
humanqa doctor

The same validated CLI is also available from the HumanQA npm organization:

npm install --global @humanqa/cli
humanqa doctor

Install the version-matched Chromium runtime once:

humanqa install-browser

First audit

humanqa init --name "My web application" --url http://127.0.0.1:3000
humanqa verify --config humanqa.yml

init writes a safe Quality Contract and a validated local journey at humanqa/journeys/smoke.yaml. Review and adapt that data-only journey as the product flow evolves; no repository clone is required.

Every run writes JSON, Markdown, standalone HTML, SARIF, and JUnit XML under humanqa-output/<timestamp>/.

Commands

humanqa init
humanqa audit <url>
humanqa verify --config humanqa.yml
humanqa generate-test <report.json>
humanqa list-packs
humanqa validate-pack <path>
humanqa install-browser [--with-deps]
humanqa doctor [--json]
humanqa github comment --report <report.json> --dry-run

Safety defaults

  • Safe mode, redaction, and screenshots are enabled by default.
  • --offline requires a loopback target and blocks cross-origin requests.
  • High-impact and mutation-capable actions are blocked unless explicitly enabled.
  • No hidden telemetry or automatic artifact upload is included.
  • Optional LLM enrichment is disabled and cannot change deterministic gates.

Use --no-screenshots for sensitive targets. Text redaction cannot guarantee that domain-specific personal information is removed from visual artifacts or traces.

Scope

HumanQA makes strong completion claims only for declared journeys. Automated accessibility checks do not establish WCAG conformance, legal compliance, screen-reader usability, or the absence of barriers in untested states.

Project documentation, examples, starter packs, and contribution guidance live at github.com/Hotragn/humanqa.

License

Apache-2.0