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

promaster

v1.6.0

Published

Interactive CLI to browse Markdown (blog/memory/books) from a public GitHub repo and save it as browser-ready HTML.

Readme

promaster

Interactive CLI to browse Markdown from a public GitHub repo, grouped into three categories: blog, memory, books. Each selected file is rendered to a styled, standalone HTML page and opened in your browser — nothing is saved to disk.

The package ships only the CLI. Your Markdown content lives in your own GitHub repo and is fetched at runtime — it is never bundled into npm.

Install

Standalone binary (no Node.js required)

Download the file for your OS, then run it directly:

| OS | Download | Run | |----|----------|-----| | Windows x64 | promaster-win.exe | .\promaster-win.exe list | | macOS (Apple Silicon) | promaster-mac-arm64 | chmod +x promaster-mac-arm64 && ./promaster-mac-arm64 list | | macOS (Intel) | promaster-mac-x64 | chmod +x promaster-mac-x64 && ./promaster-mac-x64 list | | Linux x64 | promaster-linux | chmod +x promaster-linux && ./promaster-linux list |

macOS: on first launch Gatekeeper may block it — System Settings → Privacy & Security → Open Anyway, or xattr -d com.apple.quarantine promaster-mac-arm64.

Via npm (requires Node.js ≥ 18)

npm install -g promaster

Content repo layout

One public repo with three top-level folders, each holding .md files:

your-repo/
├── blog/
├── memory/
└── books/

Usage

promaster list
  1. Pick a category: blog / memory / books.
  2. Files are listed newest → oldest (by last git commit date).
  3. Toggle one or more with space, confirm with enter.
  4. Each selection is rendered to HTML in a temporary directory and opened in your default browser right away.
  5. Press Enter in the CLI when you're done — the temporary files are deleted. Nothing is ever written to your project directory.

The pages render fully offline (styles are inlined, with light/dark support).

Configuration

Source repo is resolved in this order:

  1. PROMASTER_REPO=owner/repo environment variable
  2. "promaster": { "repo": "owner/repo" } in the current directory's package.json
  3. The DEFAULT_REPO constant in src/config.js
PROMASTER_REPO=cavid/my-notes promaster list

Optional GITHUB_TOKEN raises the unauthenticated rate limit (60/hr → 5000/hr):

GITHUB_TOKEN=ghp_xxx promaster list

License

MIT