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

@tracebird/cli

v0.1.1

Published

tracebird CLI — a local OTLP receiver and time-travel UI for AI agent runs.

Readme

@tracebird/cli

The public face of tracebird. A single npx away from a local, time-travel debugger for your AI agent runs.

npx @tracebird/cli           # start the OTLP receiver (+ UI, from Stage 3)

Then point any OpenTelemetry-instrumented agent at it:

export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318

Commands

| Command | Description | | --- | --- | | tracebird / tracebird live | Start the OTLP receiver, capture spans, and serve the UI. | | tracebird demo | Serve the UI with bundled sample runs — no agent needed. | | tracebird open <file.jsonl> | Load a saved session and serve the UI (no receiver). |

JSON API

The UI reads a small read-only API (everything delegates to @tracebird/core):

| Route | Returns | | --- | --- | | GET /api/session | { live, filePath, count } | | GET /api/runs | run summaries, newest first | | GET /api/runs/:id | a full reconstructed Run |

Options

| Flag | Default | Description | | --- | --- | --- | | --port <n> | 4318 | Port for the receiver / UI server. | | --host <addr> | 127.0.0.1 | Address to bind. | | --out <dir> | ./.tracebird | Where captured sessions are written. | | --no-open | — | Don't open the browser on start. |

How it works

  • A tiny node:http server accepts POST /v1/traces in both OTLP/JSON and OTLP/protobuf (the SDK default). Protobuf is decoded with a vendored descriptor — no codegen step.
  • Parsing and reconstruction are delegated entirely to @tracebird/core; the CLI only does I/O.
npx nx test cli