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

buffalo-projects

v0.0.1

Published

Buffalo Projects CLI — scan codebases, log work, and keep a private, shareable Buffalo work record current from the terminal.

Readme

buffalo-projects

The Buffalo Projects CLI. Scan a codebase for the projects you've built, log work, and keep your Buffalo work record current from the terminal — private by default, shareable when you choose.

Free and open source (MIT). Buffalo Projects gives Buffalo college builders a source-backed work record that can be updated from the terminal, an AI co-pilot, and GitHub. A public profile at /b/[handle] is optional output, not the default obligation.

Install

# one-off
npx -y buffalo-projects@latest scan

# or install the `buffalo` command globally
npm i -g buffalo-projects@latest

Requires Node 18+.

Quickstart

buffalo login                 # device-code login in your browser
buffalo auth                  # confirm this machine is connected
buffalo record                # preview a private work record from this repo, no login required
buffalo record --save         # save .buffalo/record.md, projects.json, and work.jsonl locally
buffalo export mentor-update  # turn the local record into a sendable update
buffalo scan                  # detect projects in the current repo, pick which to add
buffalo log "shipped X"       # log one shipped thing to your work record

buffalo record

The first-run command. It turns the current repo into a private work-record preview without requiring auth or uploading source code.

buffalo record             # human-readable preview, writes nothing
buffalo record --json      # structured output for scripts/agents
buffalo record --markdown  # markdown preview
buffalo record --save      # write local .buffalo/ artifacts only

The preview includes the project title, summary, recent git work, source signals, missing evidence, next proof move, suggested private work entry, and a privacy receipt. --save creates .buffalo/record.md, .buffalo/projects.json, and .buffalo/work.jsonl; it does not publish or sync anything.

buffalo export mentor-update
buffalo export profile-draft
buffalo export json

Exports read the local record when present, or generate an unsaved preview from the current repo.

buffalo scan

Detects the distinct efforts in a codebase (monorepo packages, standalone tools, subprojects), then lets you choose which to add to your record. It reflects what you built — it does not judge the quality of your work. Candidates are ranked by recency/activity only; you curate use / skip / never. Chosen projects are created link-only (you publish explicitly later).

buffalo scan                  # interactive checklist
buffalo scan --dry-run        # preview candidates, write nothing
buffalo scan --yes            # non-interactive: add all detected projects
buffalo scan --json           # machine-readable output

The never choices are remembered (locally in .buffalo/ignore.json and synced to your account) so they don't reappear on future scans.

Commands

buffalo login
buffalo auth      [--json]
buffalo record    [--days <n>] [--save] [--markdown] [--json]
buffalo export    mentor-update|profile-draft|json [--json]
buffalo scan      [--days <n>] [--dry-run] [--yes] [--json]
buffalo log       <what you shipped> [--note <text>] [--project <id>]
buffalo init      [--template <type>]
buffalo new       --from <example-id>
buffalo lint      [project.md]
buffalo add       evidence <file-or-url> [--caption <text>]
buffalo add       milestone <title> [--note <text>]
buffalo capture   [--days <n>] [--accept <id,id|all>]
buffalo preview
buffalo push | pull | diff | status | ci | config | examples

Add --json to any command for scriptable output.

Auth

buffalo login stores a token in your OS keychain (falling back to ~/.config/buffalo/config.toml). You can also set BUFFALO_TOKEN and BUFFALO_BASE_URL in the environment.

Run buffalo auth or buffalo whoami to verify the account connection before using hosted commands such as buffalo scan, buffalo log, buffalo push, or MCP-backed writes.

License

MIT — see LICENSE.