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-gh-footer

v0.1.1

Published

Compact GitHub PR status for pi-footer

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

championswimmerchampionswimmer

Keywords

pi-packagepi-extensiongithub

Readme

pi-gh-footer

Compact PR status for Pi + pi-footer:  #41208 ·  3  1. Nerd Font glyphs, colored passed/running/failed indicators (only nonzero states appear), and an OSC 8 link on only the PR number.

Maple Mono NF:

PR footer in Maple Mono NF

Victor Mono Nerd Font:

PR footer in Victor Mono Nerd Font

Requires git, authenticated gh, a Nerd Font, and an OSC 8-capable terminal.

pi install npm:pi-footer
pi install npm:pi-gh-footer

Disable pi-pr-status if installed (it writes the same status key); reload Pi. In /footer, choose one of:

  • Extension Status: externalStatusKey: "pr-status" — complete summary, compatible with existing footer config. Use fg: "default", no extra icon.
  • Event Value: set widgetId to any ID below and arrange/style widgets in pi-footer. Events use pi-footer:update-widget with { widgetId, value: string | null }; missing PRs clear values.

| Event widget ID | Value | | --- | --- | | gh-pr | complete colored summary | | gh-pr-number | linked #41208 | | gh-pr-state-icon / gh-pr-state | colored PR icon / open, merged, closed | | gh-pr-checks | colored check-circle / clock / x-circle + counts | | gh-pr-passed / gh-pr-running / gh-pr-failed | nonzero counts (otherwise cleared), for custom icons/colors | | gh-pr-repo / gh-pr-title | repository / title |

Example custom widgets: gh-pr-number with icon , then the three raw counts with icons , , and foregrounds green/yellow/red. The current branch's PR takes priority; otherwise a PR URL in user input is used. Updates every 30 seconds.

Development: npm ci && npm test && npm run typecheck. Screenshots: vhs demo/maple-mono.tape / vhs demo/victor-mono.tape (from repo root; install the named fonts first).

Releasing

The first release (0.1.0) is published manually with npm publish --access public after logging in to npm. Do not push v0.1.0 after publishing it: the workflow would try to publish the same version again.

For subsequent releases, update the version in package.json and package-lock.json (for example, npm version patch --no-git-tag-version) and merge the change into main. Tag that commit with the matching version (for example, git tag v0.1.1 && git push origin v0.1.1). The release workflow checks the tag, runs typechecking and tests, and publishes to npm using trusted publishing. Stable releases use the latest dist-tag; prereleases use next.

Configure the npm trusted publisher for GitHub Actions with owner championswimmer, repository pi-gh-footer, workflow release.yml, no environment, and permission to publish. No npm token secret is needed.