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

pierre-review

v0.1.23

Published

Dashboard for tracking your team's GitHub PR activity across repos — local (SQLite + gh) or self-hosted multi-tenant cloud (Postgres + GitHub App).

Readme

pierre-review

A local-only dashboard for tracking your team's GitHub PR activity across multiple repositories. Run it on your machine, see at a glance who's doing what, which PRs are stalled, which review threads are sitting untouched, and what needs your attention right now — all rendered as an interactive timeline.

There's no hosted backend, no database server, and no stored credentials. It authenticates by shelling out to your already-logged-in gh CLI, syncs activity into a local SQLite file, and serves the dashboard from a single local process.

Quick start

npx pierre-review

This starts the server, prints a local URL, and opens your browser to it.

Or install globally and use the short command:

npm install -g pierre-review
pierre

Prerequisites

  • Node.js ≥ 20.

  • GitHub CLI, installed and authenticated. Install it from https://cli.github.com, then run:

    gh auth login

    pierre reads your team's activity using your gh token. It pre-checks this on startup and exits with a friendly message if gh is missing or not authed.

Native module note: pierre-review depends on better-sqlite3, a native addon. npm installs a prebuilt binary for common platforms; if none matches your Node/OS/arch, npm compiles it from source on install (needs a C++ toolchain — Xcode Command Line Tools on macOS, build-essential + Python on Linux, MSVC build tools on Windows).

Usage

pierre [options]
pierre-review [options]

| Flag | Env | Default | Description | |------|-----|---------|-------------| | --no-open | NO_OPEN | — | Don't open the browser on start. | | --port <n> | PORT | 4000 | Port to listen on. | | --db <path> | DATABASE_URL | ~/.pierre-review/pierre-review.sqlite | SQLite DB path. | | — | PERSIST_BODIES | false | Store full comment/PR text in the DB instead of loading it on demand (larger DB, but PR detail works fully offline). | | -h, --help | — | — | Show usage. |

Examples:

pierre --port 4123 --no-open
pierre --db /tmp/pierre.sqlite

Data directory

By default the local SQLite database lives at:

~/.pierre-review/pierre-review.sqlite

The directory is created automatically. Override the location with --db or the DATABASE_URL environment variable. No team activity data or credentials are ever sent anywhere — everything stays on your machine.

How it works

Once running, open the printed URL (default http://localhost:4000). Add the repositories you want to watch from the in-app picker; the app syncs their PR activity (full backfill on first sync, incremental every few minutes thereafter) into your local DB and renders it as a timeline.

To keep the database small and backfills fast, bulky text — PR/comment/review bodies and diff hunks — isn't stored; it's fetched from GitHub (using your gh token) the first time you open a PR and cached in your browser, so re-opening an unchanged PR is instant and offline. Set PERSIST_BODIES=true to store that text locally instead — a larger database, but PR detail then works fully offline.

License

MIT