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

@brela-dev/cli

v0.1.2

Published

Silent AI code attribution and governance tool for engineering teams

Readme

@brela-dev/cli

CLI for Brela — set up AI code attribution in any project with one command.

Brela runs silently in the background and tracks which AI tools wrote which lines: GitHub Copilot, Claude Code, Cursor, Windsurf, Cline, Aider, Continue, and more. All data stays local — nothing leaves your machine.

Install

npm install -g @brela-dev/cli

Commands

brela init

One-command project setup. Run once in your project root:

cd your-repo
brela init

What it does:

  • Adds shell wrappers to .zshrc / .bashrc so claude and gh copilot log intent before running
  • Installs the brela-vscode VS Code extension
  • Starts the background daemon that watches for agent file writes
  • Creates .brela/ session directory and git pre-commit hook

brela report

Print an AI attribution breakdown:

brela report              # today
brela report --days 7     # last 7 days
brela report --from 2024-01-01 --to 2024-01-31

brela explain <file>

Full attribution history for a specific file:

brela explain src/utils/api.ts
brela explain src/utils/api.ts --days 30
brela explain src/utils/api.ts --json
brela explain src/utils/api.ts --since 2026-03-01

Shows:

  • Attribution summary (tools, events, chars inserted)
  • Timeline of every AI event in that file
  • Risk assessment (unreviewed AI sections, test coverage)

brela daemon

Control the background file-watcher daemon:

brela daemon start
brela daemon stop
brela daemon status

Started automatically by brela init.

brela hook

Manually install or uninstall git hooks:

brela hook install
brela hook uninstall

Session data

All data is local to your project under .brela/ (gitignored automatically):

.brela/
  sessions/            # NDJSON attribution log, one file per day
  shell-intents.jsonl  # written by shell wrappers before AI CLI runs
  daemon.pid

Part of Brela

See the root repo for the VS Code extension and full documentation.