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-packages

v0.1.0

Published

In-TUI package manager for pi. Adds /packages that lists every configured package with version numbers, detects available updates on demand, and installs / updates / removes packages by orchestrating the pi CLI.

Readme

pi-packages

In-TUI package manager for pi. Adds a /packages command: list every configured package with version numbers, detect available updates on demand, and install / update / remove — all without leaving the TUI.

Status: 📝 Draft (PRD only — not yet implemented).

The full product spec, technical design, open questions, and phasing live in PRD.md. Treat that file as the source of truth until implementation begins.

Why

pi list shows package names, install paths, and git refs — but not npm version numbers, and there's no in-TUI way to manage packages or see what's outdated. pi-packages closes that gap:

  • See versions for everything in one screen (the direct answer to "where can I see installed packages and their versions?").
  • Detect updates on demand (npm registry latest vs. installed; git remote vs. pinned ref).
  • Install / update / remove from the TUI by orchestrating the pi CLI.

Command surface

| Command | Action | |---|---| | /packages (alias /pkg) | open the interactive package manager | | /packages <src> | jump straight to installing <src> |

Architecture (summary)

  • Reads parse settings.json + each package's package.json directly (offline, accurate, includes versions).
  • Mutations shell out to the pi CLI (pi install / remove / update) — pi's PackageManager is the right abstraction but is not exposed to extensions.
  • Restart required to apply changes — pi has no hot-reload path (verified). See PRD §8.7 / Appendix E.

Status & next steps

  1. Review and sign off on PRD.md — especially Open Questions OQ1 (restart API) and OQ4 (default install scope).
  2. Scaffold the package (package.json, src/) per PRD Appendix layout.
  3. Implement MVP phase (PRD §11).

Owned-and-published package, following the release flow in the parent AGENTS.md (tag-driven GitHub Actions + npm Trusted Publisher; never npm publish from a laptop).