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

omniqa

v0.8.0

Published

OmniQA: agentic test framework and product knowledge base. SDK, runner and CLI.

Readme

OmniQA

OmniQA is an AI-first testing tool. Point it at your product (the site, the repositories, the docs) and its agent interviews you, learns how the product works, plans the tests with you, writes them as plain-English tests on top of its own browser driver (Chrome for Testing over the DevTools protocol), runs them on its own runner, and keeps the knowledge and the tests current as the product changes.

  • Agentic tests. Steps are written the way a user acts (agent.do("click Add to cart")); a model finds the element in a screenshot of the page, and code confirms it is really there at that point before acting, so there are no selectors to maintain. API tests stay deterministic.
  • Security tests, if you choose them. A third kind, for the production tier, in a browser behind Interceptor, a local proxy OmniQA installs on request. A guard fails when a weakness shows up that the test does not list as accepted; basic checks, by OWASP Top 10 category, ask the product what it must refuse (a request without its session or with another member's, a forged request, a parameter handed markup or a quote). Code plans, writes and runs them: no model call. With securityScan: on for an environment, an agent scan follows them: a security researcher that sends requests of its own, within gates that are code, and a security reviewer, another model, that confirms or discards each claim. What they find is in a report outside git.
  • A product knowledge base. Built from your code, your docs and the running product, reviewed by a second model, and used by every agent.
  • Self-maintaining. A product change on GitHub or GitLab updates the knowledge and the affected tests; heals and fixes arrive as a commit or a merge request, each judged by a reviewer model. For functionality a change adds, OmniQA proposes tests and you choose which are written.
  • Web and native. Desktop and mobile browsers through OmniQA's own driver on Chrome for Testing (phones by emulation, or the real Chrome of an Android device over adb), stock Firefox over WebDriver BiDi (optional), Safari on an iOS simulator, and iOS, Android, macOS and Linux apps through agent-device.
  • Your models. Anthropic or any OpenAI-compatible provider (OpenRouter, a local server), with your own key; the model that runs the steps must read images.

A test OmniQA writes:

import { test, expect } from "omniqa/test";

test("cart-1: A guest adds a widget to the cart", { tag: ["@dev", "@e2e"] }, async ({ page, agent }) => {
  await page.goto("/");
  await agent.do("click the Add to cart button");
  await agent.assert("the cart shows 1 item");
  await expect(page).toHaveURL((url) => url.pathname === "/");
});

Install

Node.js 26.6 or later and git. A model key: Anthropic (ANTHROPIC_API_KEY) or an OpenAI-compatible provider such as OpenRouter (OPENROUTER_API_KEY).

npm install -g omniqa
omniqa install                 # the Chrome for Testing build OmniQA pins (Linux: --with-deps adds its libraries)
omniqa doctor                  # checks this machine; exit code 0 means ready

Start a project

One folder per product, usually a qa/ folder in the product's repository or a repository of its own:

omniqa init shop-qa            # creates the folder (and a git repository in it) and asks about your product
cd shop-qa
cp .env.example .env           # the model key and the test accounts go here, never in git
omniqa plan                    # the test plan, its reviewer, your approval on a page in your browser
omniqa knowledge build         # the knowledge base
omniqa write --priority P0     # write the P0 tests
omniqa test                    # run them
omniqa security                # the security tests alone, if you chose them; the agent scan after them where it is on
omniqa coverage                # what is covered, as a page in your browser (--tree: in the terminal)
omniqa scheme                  # the product scheme as a page in your browser
omniqa chat                    # ask the QA agent anything about it

omniqa init without a folder runs the stages in one go: the interview, the plan, the knowledge base, the writer. Run it again and it resumes where it stopped.

Documentation

  • README on GitHub: how it works, cost, and using it on your product.
  • Install guide: every step with the expected output, on a sample shop, then your product.
  • Reference: every command, file and switch.
  • Devices: mobile browsers, simulators, emulators and native apps.
  • Issues.

The CLI, the test SDK (omniqa/test) and the MCP server live in this package; @omniqa/core, @omniqa/browser, @omniqa/web, @omniqa/device, @omniqa/github and @omniqa/gitlab are its parts and come with it.

Apache-2.0.