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

@flakytests/cli

v0.1.0

Published

Framework-independent flaky test detection, quarantine and recovery

Readme

@flakytests/cli

Detect flaky tests, quarantine repeated flakes, and automatically recover stable tests without disabling them. Supports Playwright and Vitest 3.2, uses Git for state, and needs no external database. Requires Node.js 22+. MIT licensed.

npm install --save-dev @flakytests/cli

Core, both adapters, and the Git provider install automatically. Vitest users should also install @flakytests/adapter-vitest directly and use its @flakytests/adapter-vitest/reporter export instead of ordinary JSON reporting.

Create flaky.yml in your repository:

quarantine:
  flakyIncidents: 2
  window: 10
recovery:
  consecutivePasses: 10
state:
  provider: git
  branch: flaky-state
adapters:
  playwright:
    results: test-results/playwright.json

Configure Playwright's JSON reporter with retries, run your tests, then:

npx flaky evaluate
npx flaky status
npx flaky quarantine 'playwright:example.spec.ts::test title' --actor alice --reason 'Investigating'
npx flaky unquarantine 'playwright:example.spec.ts::test title' --actor alice

mark and unmark manage the known-flaky flag independently of quarantine. All manual actions require an actor and retain an audit record.

The evaluator creates flaky-state on origin automatically. It exits 1 for unquarantined hard failures, 0 for passes/flakes/quarantined failures, and 2 for invalid reports or operational errors. State must persist before CI passes.

In CI, allow the raw test command to fail, then use flaky evaluate as the final required gate. Pass the original exit code using --test-exit-code. Remove stale reports before testing, evaluate each report once, exclude flaky-state from workflow triggers, and restrict writes to automation. Do not expose write credentials to untrusted pull-request code.

See the project documentation for reporter configurations, GitHub Actions examples, and policy details.