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

boardq

v0.3.0

Published

Join a BoardQ Claude Code tokens leaderboard and report your token spend automatically.

Downloads

898

Readme

boardq

Join a BoardQ Claude Code tokens leaderboard and automatically report how many tokens you spend — compete with your team or the world for the top spot.

npx boardq join <boardId> --token <your-token>

You get your personal --token from the leaderboard page (open the board on boardq.io and click Join this leaderboard).

How it works

  • Runs boardq join once. It installs a Claude Code hook that reports your usage automatically after each session — no terminal needs to stay open.
  • Reads Claude Code's own local usage logs in ~/.claude/projects/**/*.jsonl (the same data ccusage uses). Nothing else is sent — just your token totals and an estimated cost.
  • The moment you join is your baseline: only tokens you spend after joining count toward your score. Your historical usage is never uploaded or ranked.
  • Reports are throttled to at most once every ~5 minutes, plus a final flush when a session ends.

Commands

| Command | What it does | | --- | --- | | boardq join <boardId> --token <t> | Join a board and install auto-updating hooks | | boardq report <boardId> | Send a single update now | | boardq uninstall [boardId] | Remove the auto-update hooks | | boardq status | Show your local token usage (nothing is uploaded) | | boardq help | Show help |

join options

| Flag | Default | Description | | --- | --- | --- | | --token <t> | — | Your personal token (required) | | --name <n> | — | Override your display name | | --no-hook | — | Don't install the hook (report once and exit) | | --watch | — | Keep the terminal open and report on a timer instead | | --interval <m> | 15 | With --watch, minutes between reports | | --once | — | Report a single time and exit | | --api <url> | production | Override the API base URL |

Privacy

boardq never reads the contents of your prompts or code — only the token-count and model fields Claude Code records for each turn. Config (your board token) is stored at ~/.config/boardq/config.json with 600 permissions.

Requirements

  • Node.js ≥ 18
  • Claude Code installed and used at least once

Learn more: https://www.boardq.io/tokens-leaderboard