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

buildstory

v0.2.0

Published

Automatically capture the story of what you build

Readme

buildstory

Automatically capture the story of what you build. Buildstory installs a git post-commit hook that silently ships commit metadata to a server, which uses AI to turn raw commits into human-readable project updates. Review, approve, and publish a public timeline of your work from the web dashboard.

Installation

npm install -g buildstory

Quick start

# 1. Save your API key
buildstory auth

# 2. Initialize in a git repo
cd your-project
buildstory init

# 3. Code and commit as usual — Buildstory captures each commit automatically
git add . && git commit -m "add user profiles"

# 4. Review and approve updates on the dashboard

Commands

| Command | Description | |---|---| | buildstory auth | Save your API key (stored in ~/.buildstory/credentials.json) | | buildstory init | Initialize Buildstory in the current git repo | | buildstory --help | Show help | | buildstory --version | Show version |

buildstory init options

| Flag | Description | Default | |---|---|---| | -e, --endpoint <url> | API endpoint | https://buildstory-cli.vercel.app |

You can also set the endpoint via the BUILDSTORY_ENDPOINT environment variable.

What data gets sent

Each commit sends the following to the Buildstory server:

  • Commit hash, message, timestamp, and author
  • Diff stats (files changed, insertions, deletions)
  • List of changed files with per-file stats
  • A truncated diff summary (first 50 lines of git diff --stat)
  • Detected environment (Cursor, VS Code, shell, OS)

Secret redaction: The hook automatically redacts API keys, tokens, private keys, AWS keys, and connection strings from diff summaries before sending.

Files matching patterns in .buildstoryignore are excluded from the payload entirely.

Configuration files

| File | Scope | Purpose | |---|---|---| | ~/.buildstory/credentials.json | Global | API key for authentication | | .buildstory/config.json | Per-repo | Project ID, endpoint, machine ID | | .buildstoryignore | Per-repo | Glob patterns for files to exclude from commit data |

The .buildstory/ directory is automatically added to .gitignore during init.

License

MIT