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

@dispatch-triage/eval

v0.1.0

Published

Calibration and accuracy reporting: reliability diagrams, ECE, threshold recommendations.

Readme

@dispatch-triage/eval

Calibration and accuracy measurement.

Part of Dispatch Triage — programmable triage for GitHub. Behind dispatch eval; import it directly to measure a decision log yourself.

npm i @dispatch-triage/eval

This is the feature that needs probabilities to mean something. A model claiming 0.8 should be right about 80% of the time; if it is not, every threshold in every config is decorative and the gate ladder is theatre.

What it measures

  • Reliability diagram — predictions bucketed by confidence, claimed accuracy against observed. Empty bins stay in the output: a diagram with gaps is honest about where there is no evidence.
  • Expected calibration error — the average gap, weighted by bin population. Reported alongside the worst bin, because ECE happily hides one badly-wrong bucket.
  • Per question — sorted most over-confident first, so the question to fix is at the top.
  • Threshold recommendation — the lowest confidence at which accuracy still clears a target, never below the lowest confidence actually observed, and never on fewer than 20 predictions.

The bias, stated plainly

Dispatch has no ground truth. What it has is maintainers overriding it: removing a label it applied, or adding one it held back. A prediction counts as correct when nobody corrected it — which means silence counts as agreement.

That overstates accuracy on items nobody looked at. The honest reading of any number this package produces is "accuracy among items a maintainer actually reviewed", and the CLI says so under the report whenever there are no corrections yet.

Why a recommendation can be refused

Three ways, all deliberate:

  • insufficient_data — fewer than 20 predictions. A threshold derived from six samples is a guess wearing a number.
  • never_reaches_target — accuracy never clears the target at any threshold. That usually means the rules are asking the wrong questions, not asking them badly.
  • A drift smaller than 0.05 is not reported at all. Nudging a maintainer from 0.85 to 0.84 every week trains them to ignore the report.

CLI reference · Documentation · Repository

MIT