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

rbrain

v0.1.2

Published

Local-first engineering risk intelligence for a single repository

Downloads

499

Readme

rbrain

Local-first engineering risk intelligence for a single repository.

Before you edit code, rbrain answers:

  1. What likely breaks if I change this?
  2. Who owns this code today?
  3. What depends on this — transitively?
  4. What changed recently here?
  5. What got riskier this week?
  6. What is fragile / weakly tested?
  7. What files tend to change together with this one?

Status: V1 in early build. Today only init is implemented; scan, risk, deps, owners, hotspots, audit, ask, create-context arrive in subsequent milestones.

Install

npm install -g rbrain

This installs two equivalent commands: rbrain (short) and repobrain (alias).

Quickstart

cd path/to/your/repo
rbrain init

This creates .repobrain/, writes a default config.json, and appends .repobrain/ to your .gitignore. Idempotent — re-running reports already initialized; no changes.

What it is — and is not

It IS a deterministic engine over your repo state + git history, run locally, with no network calls during a default scan, no repo upload, and no code execution from the analyzed repo.

It is NOT a code generator, NOT code search, NOT a repo chatbot, NOT a linter, and NOT a manager KPI dashboard.

Flags

rbrain [command] [options]

Options:
  --cwd <path>    repository root (defaults to the current working directory)
  --json          emit machine-readable JSON
  --quiet         suppress non-essential output
  --verbose       verbose output
  -V, --version   print the version
  -h, --help      print help

License

MIT.