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/observe

v0.4.0

Published

Iris observability — OTel-shaped spans derived from a recorded session's inspection (root turn span + child effect spans + marker spans), with deterministic spanIds (sessionId#seq, no RNG) and timing from record.ts. Emitted to an injected Sink (collecting

Readme

@irisrun/observe

OTel-shaped spans, derived from the journal — determinism intact. Your agent already recorded everything it did. This turns a recorded session's inspection into spans, so observability is a projection of the journal, not a side effect woven through the engine. A turn that was observed still replays byte-identically.

What it is

toSpans(inspection) takes a SessionInspection (from @irisrun/inspect) and returns OTel-shaped Span[]: a root turn span parenting one child per effect (intent→result, carrying its outcome) and one per marker. spanIds are DETERMINISTIC — sessionId#seq, no RNG — so re-spanning is byte-identical; timing reads the journal's recorded ts.

Emission goes through an injected Sink (export(spans)), decoupling spans from any backend: collectingSink() accumulates in memory (for tests), consoleSink() prints one JSON span per line. Real OTLP export is a gated manual smoke. Depends on @irisrun/core + @irisrun/inspect only.

Use it

import { toSpans, collectingSink } from "@irisrun/observe";
import { inspectSession } from "@irisrun/inspect";

const { sink, spans } = collectingSink();
await sink.export(toSpans(await inspectSession(store, "s1")));

See docs/Observability.


Part of Iris — own, portable, verifiable state.