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

flaky-test-tracker

v0.1.0

Published

Local pass/fail history tracker that finds flaky tests by flip rate and lets you quarantine them.

Readme

flaky-tracker

Local pass/fail history tracker for your test suite. Record test run results over time, rank tests by flip rate to spot flaky ones, and quarantine them without touching your test framework's config.

Zero runtime dependencies. Node.js >= 18.3.0.

Install

npm install -g flaky-tracker

Usage

# record a run result (call this from your CI after each test)
flaky-tracker record my.test.spec pass
flaky-tracker record my.test.spec fail

# see which tests flip the most
flaky-tracker rank
flaky-tracker rank --window 20   # only consider the last 20 runs

# inspect one test
flaky-tracker show my.test.spec

# quarantine a known-flaky test
flaky-tracker quarantine my.test.spec

# export the quarantine list for your CI to exclude
flaky-tracker export-quarantine
flaky-tracker export-quarantine --format csv

flaky-tracker unquarantine my.test.spec

All commands accept --file <path> (or --file=<path>) to point at a custom data file. Default: ./.flaky-tracker/data.json in the current directory.

Flip rate

For a test's recent N runs (all runs by default, or the last N with --window N):

flipRate = flipCount / max(1, observations - 1)

A "flip" is any adjacent pair of runs where the status changed (pass→fail or fail→pass). Fewer than 2 recorded runs always gives a flip rate of 0.

Quarantine

export-quarantine prints quarantined test ids (one per line, or comma-separated with --format csv). Wire the output into your test runner's exclude flag, e.g.:

flaky-tracker export-quarantine --format csv
# pytest -k "not ($(flaky-tracker export-quarantine --format csv | tr ',' '|'))"

flaky-tracker does not parse test framework output or modify test configs — you (or your CI script) call record after each run, and consume export-quarantine for exclusion.

License

MIT