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-echo-statusline

v0.1.0

Published

Configurable status line rendered from one shell command's output

Readme

pi-echo-statusline

A configurable status line via one shell command.

Design note

Today, a custom status line on Pi means writing a whole extension (see Pi's own official status-line.ts example). This package makes it a config file instead. Refreshed on session_start and after every turn_end — not on a fixed wall-clock timer, a deliberate scope simplification (no timer to clean up on session_shutdown, no risk of a runaway interval). The command receives a JSON payload on stdin (cwd, model, session_id, context usage) using only fields actually available from ExtensionContext. Output is rendered as-is (first line, trimmed) via ctx.ui.setStatus().

Live-verified against a real completed turn, not just type-checked: both refreshes fired with correct data — session_start reported {tokens: 0, ...} before any turn, and the post-turn_end refresh correctly reported {tokens: 2979, ...} matching the actual usage from that real turn, with the correct live model id (gpt-5.5) and context window (272000) flowing through.

Usage

Configure in .pi/echo/statusline.json (project) or ~/.pi/agent/echo/statusline.json (global; project wins outright — a status line is one choice, not additive):

{ "command": "./scripts/statusline.sh", "timeout": 5000 }

/statusline shows the configured command and refreshes it immediately.