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

@agents-forge/qa-reporter

v1.0.0

Published

AI QA Reporter agent — runs Playwright tests and writes a plain English summary report for stakeholders. v2.0 will add Allure report integration.

Readme

📊 QA Reporter Agent

npm version

Runs your Playwright tests and writes a plain English summary_report.md that any stakeholder can understand — with failed test explanations, recommendations, and next steps.

Part of the @agents-forge AIQA pipeline:

analyst → qa-planner → qa-engineer → qa-reviewer → qa-reporter

v1.0 uses Playwright's built-in JSON reporter. v2.0 will add Allure report integration for richer analytics.


Install

npm install @agents-forge/qa-reporter
npm install --save-dev @playwright/test
npx playwright install chromium

Quick Start

# Run all tests + generate stakeholder report
npx @agents-forge/qa-reporter

# Smoke tests only
npx @agents-forge/qa-reporter --grep @smoke

Authentication

Auto-detected — no config needed:

| Method | Setup | |---|---| | Anthropic API key | ANTHROPIC_API_KEY=sk-ant-... in .env | | Claude subscription | npm install -g @anthropic-ai/claude-code → claude login | | GitHub Copilot | gh auth login |


Features

  • 🎭 Runs Playwright tests — with optional grep filter or spec file
  • 📖 Reads JSON results — parses Playwright's built-in JSON reporter
  • 📝 Writes summary_report.md — plain English for stakeholders
  • ❌ Explains failures — error messages + likely cause + recommended fix
  • 📋 Cross-references review_report.md — flags predicted vs actual failures
  • 🔐 Multi-provider auth — API key, claude login, or GitHub Copilot
  • 🔄 Results-only mode — skip test run, just report on existing results

CLI Usage

# Run all tests
npx @agents-forge/qa-reporter

# Filter by tag
npx @agents-forge/qa-reporter --grep @smoke
npx @agents-forge/qa-reporter --grep @regression

# Custom output
npx @agents-forge/qa-reporter --output sprint_23_report.md

# Single spec file
npx @agents-forge/qa-reporter --spec tests/login.spec.ts

# Read existing results (no test run)
npx @agents-forge/qa-reporter --results-only

# Different directory
npx @agents-forge/qa-reporter --dir ./my-project

Programmatic Usage

import { runQAReporter } from "@agents-forge/qa-reporter";

const result = await runQAReporter({
  grep: "@smoke",                    // optional tag filter
  specFile: "tests/login.spec.ts",   // optional specific file
  outputFile: "smoke_report.md",     // optional output name
  cwd: process.cwd(),                // optional directory
  resultsOnly: false,                // optional skip test run
});

console.log(`Passed: ${result.passed}, Failed: ${result.failed}`);

Output: summary_report.md

# Test Execution Report
Status: ✅ PASSED / ❌ FAILED / ⚠️ PARTIAL

## Results Summary
| ✅ Passed | ❌ Failed | ⏭️ Skipped | 🔄 Flaky | Total | Duration |

## Test Suite Breakdown
| Module | Passed | Failed | Skipped | Duration |

## ❌ Failed Tests
(with error message, likely cause, recommended fix per test)

## 🔄 Flaky Tests
## ⏱️ Performance (slowest tests)
## Browser Matrix Results
## Known Issues Cross-reference
## Recommendations
## Next Steps

Playwright Config Requirements

Your playwright.config.ts must include the JSON reporter:

reporter: [
  ["json", { outputFile: "test-results/results.json" }],
  ["html", { outputFolder: "playwright-report" }],
]

This is automatically configured if you used @agents-forge/qa-engineer.


Full Pipeline

npx @agents-forge/analyst https://my-app.com requirements.md
npx @agents-forge/qa-planner requirements.md test_plan.md
npx @agents-forge/qa-engineer test_plan.md --url https://my-app.com
npx @agents-forge/qa-reviewer
npx @agents-forge/qa-reporter --grep @smoke

Roadmap

| Version | Reporter | Status | |---|---|---| | v1.0 | Playwright built-in JSON | ✅ Current | | v2.0 | Allure Reports | 🔲 Planned |


Troubleshooting

| Error | Fix | |---|---| | Playwright not found | npm install --save-dev @playwright/test | | playwright.config.ts not found | Run @agents-forge/qa-engineer first | | No JSON results file found | Add JSON reporter to playwright.config.ts | | Authentication failed | Set ANTHROPIC_API_KEY or run claude login | | Tests fail on CI | Set BASE_URL env var in your CI config |


License

MIT