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

@nodetool-ai/reliability-harness

v0.8.1

Published

Reliability harness core: journey manifests, RunRecord, normalization, and per-channel stream diff (docs/RELIABILITY_ARCHITECTURE.md §12)

Readme

@nodetool-ai/reliability-harness

Core of NodeTool's reliability harness: journey manifests, the RunRecord format, output normalization, and per-channel stream diffing.

A journey replays a scripted workload against a driver and records everything it emitted as a RunRecord. Normalization strips the parts that legitimately change between runs (ids, timestamps, durations) so two records compare on behavior alone; the diff is per channel, so a change in log output does not mask a change in results.

Layout

| Path | Holds | |---|---| | core/journey.ts | Journey manifest schema and loading | | core/record.ts | RunRecord — what one replay captured | | core/normalize.ts | Run-to-run variance stripped before comparison | | core/diff.ts | Per-channel stream diff | | core/golden.ts | Golden-record read/write | | core/invariants/ | Assertions that must hold across every journey | | drivers/ | What a journey drives | | faults/ | Fault injection |

Usage

npm install @nodetool-ai/reliability-harness

The package also ships a CLI entry (cli.ts) used by the repo's Ring 0 reliability journeys, which nodetool harness gate selects for diffs touching packages/kernel/.