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

gsd-browser

v0.9.1

Published

Browse markdown artifacts that AI agents write, fresh from disk

Downloads

209

Readme

gsd-browser

Browse markdown artifacts that AI agents write, fresh from disk.

Dashboard

What is this

GSD (get-shit-done) is a Claude Code planning framework where AI agents continuously produce structured markdown artifacts — roadmaps, phase plans, research docs, state files — in a .planning/ directory as they work.

gsd-browser is a companion tool that lets you read those artifacts in a clean browser UI without leaving your workflow. Point it at your repos and get a dashboard showing project progress, phase timelines, and branch-aware milestone state. Every page load reads directly from disk — no caching, no stale content.

Quick Start

npx gsd-browser

Run in any directory. gsd-browser auto-discovers .planning/, docs/, and README.md. If found, it auto-registers the directory and opens your browser to the dashboard.

Installation

For a permanent global install:

npm install -g gsd-browser

Usage

Start the server

gsd-browser

Starts on port 4242 by default, opens browser automatically. On first run in a directory with GSD conventions, auto-registers the current directory.

CLI Reference

Source management

# Register a source directory (auto-discovers conventions)
gsd-browser add [path]

# Register with a custom display name
gsd-browser add . --name my-project

# Remove a registered source by name or path
gsd-browser remove <name|path>

# List all registered sources
gsd-browser list

Server options

--port <n>, -p <n>    Port to listen on (default: 4242)
--no-open             Suppress browser auto-open on startup
                      (save permanently: set "open": false in your config)

General

--version, -v         Print version and exit
--help, -h            Show help message

Features

  • GFM rendering with syntax highlighting (Shiki) and Mermaid diagrams rendered server-side as SVG
  • Multi-project dashboard with phase timeline and progress tracking
  • File tree browser with source switching across registered projects
  • Fresh-from-disk on every request — no caching, no stale reads
  • Convention-based discovery: .planning/, docs/, README.md auto-detected
  • Branch-aware GSD progress across git branches
  • Light and dark themes with Catppuccin colors
  • Localhost-only with Content-Security-Policy headers (security-first)

How It Works

Node.js + Fastify serves a single-page application. Markdown files are rendered server-side using markdown-it, Shiki (syntax highlighting), and Mermaid (diagram SVG generation). The frontend is vanilla JavaScript with no build step. Source registration is persisted in a config file under ~/.config/gsd-browser/.

Configuration

Config file location: ~/.config/gsd-browser/sources.json

The config stores registered source paths and the open preference (whether to auto-open the browser on startup). You can set "open": false to permanently suppress browser auto-open.

Author

Matt Stone

ko-fi

License

MIT