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

@naamanu/bragbot

v1.0.2

Published

Generate brag documents from your git history

Readme

bragbot

Generate brag documents from your git history. Inspired by Julia Evans' blog post on brag documents.

Installation

npm install -g @naamanu/bragbot

Usage

One-time Generation

Generate a brag document for any git repository:

# Current directory, last month
bragbot

# Specific repo and date range
bragbot /path/to/repo --since "2025-01-01" --until "2025-06-30"

# Output to specific file
bragbot -o my-brag.md

# Output to stdout (for piping)
bragbot --stdout | less

# Filter by author
bragbot --author "[email protected]"

Options

| Option | Description | |--------|-------------| | -s, --since <date> | Start date (default: "1 month ago") | | -u, --until <date> | End date (default: "today") | | -a, --author <name> | Filter by author name/email | | -o, --output <file> | Output file (default: brag-<start>-to-<end>.md) | | --stdout | Output to stdout instead of file |

Background Daemon

Run bragbot as a background service to automatically collect daily brag documents.

Add Repositories to Watch

# Add a repo with auto-detected settings
bragbot daemon add /path/to/repo

# Add with custom name and author filter
bragbot daemon add /path/to/repo --name "My Project" --author "[email protected]"

# Add with custom output directory
bragbot daemon add /path/to/repo --output-dir ~/brags

Manage Watched Repos

# List all watched repositories
bragbot daemon list

# Remove a repository
bragbot daemon remove /path/to/repo

Configure Schedule

# Run daily at 9 AM (default)
bragbot daemon schedule daily

# Run weekly (Mondays at 9 AM)
bragbot daemon schedule weekly

# Run at specific hour (0-23)
bragbot daemon schedule 17  # 5 PM

Start/Stop Daemon

# Start background daemon
bragbot daemon start

# Check status
bragbot daemon status

# Stop daemon
bragbot daemon stop

# Run collection once (without daemon)
bragbot daemon run

Configuration

All daemon configuration is stored in ~/.bragbot/:

| File | Description | |------|-------------| | config.json | Watched repos and schedule | | daemon.pid | Process ID of running daemon | | daemon.log | Daemon logs | | brags/ | Default output directory for collected brags |

Output Format

Bragbot generates a structured markdown document with:

  • Summary - Total commits, branches, and identified themes (features, bug fixes, etc.)
  • Work by Branch/Feature - Grouped commits with full commit descriptions
  • Detailed Commit Log - Table of all commits with dates, hashes, and messages

All data is read from local git history - no external requests are made.

Development

# Install dependencies
bun install

# Run in development
bun run dev

# Build for production
bun run build

License

MIT