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

@irisrun/evals

v0.4.0

Published

Iris reproducible-eval arbiter (spec 03 §7) — run a deterministic scenario (fresh store + scripted performers per run), then score the recorded session via @irisrun/inspect. The arbiter is reproducibility, not taste: the same case+scorer re-runs byte-iden

Readme

@irisrun/evals

Reproducible evals — because determinism makes scoring repeatable. Run the same scenario and it replays byte-identically from its journal, so a score is a fact about the run, not a roll of the dice. The arbiter is reproducibility, not taste: the same case + scorer re-runs identically; a swapped tactic scores differently, but reproducibly.

What it is

runEval runs a deterministic scenario (a fresh store + scripted performers per run) on the core runTurn, then scores the recorded session via @irisrun/inspect; runSuite runs a set; reproduce re-runs a case to confirm byte-identical replay. This is faithful record-replay of captured effects — not a claim that a live model is deterministic. Depends on @irisrun/core + @irisrun/inspect.

Use it

iris eval ./evals/suite.mjs    # reproducible scenario scoring

See docs/Audit & reproducible evals.


Part of Iris — own, portable, verifiable state.