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/runner-api

v1.13.0

Published

Runner that executes Playwright APIRequestContext specs for api test cases, after checking every case against the configured OpenAPI contract.

Readme

@qa-ai-stlc/runner-api

Implements the Runner interface (@qa-ai-stlc/core) for api test cases. Before any spec runs it loads the OpenAPI 3.x contract config.yaml names in api.source (a project file, an allowlisted URL, or discover), then checks every test case a spec declares through its testCaseId annotation: the case must be an api case, must list the contract operations it exercises in endpoints, and every one of them must exist in the contract. A case that names an operation the contract lacks rejects the whole run (API_CASE_NOT_IN_CONTRACT) before a request is sent. The contract text is stored as artifacts/api-contract.txt and registered in the manifest, so the SHA-256 a run relied on is on record.

A profile is created through the agent (qa.config_add_api_auth, qa config add api-auth) and, for a browser token, proposed by qa.browser_discover_api_auth; nobody edits YAML by hand (P6-93).

A spec authenticates only through an apiAuth profile from config.yaml (ADR-0012): it imports the generated tests/qa/api-auth.ts and calls request.get(url, apiAuth('<profile>')). The runner resolves the profiles a spec names, passes them to the Playwright process through its environment only, and scrubs their values from reported failures. A spec that writes a credential itself is rejected before it runs (HTTP_CREDENTIAL_INPUT_REJECTED), and a run that carries a credential keeps no Playwright trace, since a trace archive holds request headers.

The specs themselves are ordinary Playwright Test files using APIRequestContext; execution and result mapping reuse @qa-ai-stlc/runner-playwright.

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