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

pi-working-status

v0.1.0

Published

Replace pi's generic Working row with a live phase line — waiting/thinking/writing/calling/tool with measured timers, character counts, and quiet detection

Readme

pi-working-status

Replace pi's generic Working row with a live phase line. Everything shown is measured from the actual event stream — never estimated:

waiting 4.2s                 request sent → first token (TTFT)
thinking 3.1s · 820 ch       reasoning content streaming
writing 5.4s · 2.1k ch       assistant text streaming
calling write 1.2s           tool-call arguments being generated
bash 12.3s · 1.2k out        tool executing (out = text-block chars emitted)
write 1.4s · 300 out
· quiet 6.1s                 nothing for >3s — stalls become visible

Install

pi install npm:pi-working-status

Then /reload or restart pi.

What the numbers mean

All counts are exact per-delta sums, not estimates:

| Field | Meaning | |---|---| | waiting | time since the provider request went out, until the first delta | | thinking / ch | reasoning characters produced by this LLM call | | writing / ch | assistant text characters produced by this LLM call | | calling | tool-call arguments being streamed (shows the tool name) | | out | characters the running tool has emitted (text blocks only) | | quiet | seconds since the last event of any kind (shown past 3s) |

out counts text only. A tool that returns just images (e.g. read on a screenshot) legitimately stays at 0 — that is a real value, not a hang. Use the trailing quiet timer to tell the difference.

Notes

  • No commands, no config: installing the extension turns it on. To disable it, remove the extension (or delete the file before /reload).
  • The timer runs at 200 ms; the row only repaints when its text actually changes.
  • On agent_settled the row is cleared and the timer stops, so it never leaks into the next turn.

Requirements

  • pi on your PATH (Node ≥ 22).

License

MIT