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

aieracard

v0.1.15

Published

Generate a shareable card from your AI tool usage. Local parsing, aggregate numbers only.

Downloads

1,514

Readme

aieracard

Your AI usage — tokens, streaks, models — on one permanent, shareable card.

npx aieracard

The CLI collects usage locally from:

  • Claude Code — local JSONL logs (~/.claude/projects), fully automatic
  • Codex — local JSONL under ~/.codex/sessions (override with CODEX_HOME)
  • Cursor — all-time usage via your own cursor.com session (token resolved locally, sent only to cursor.com); CSV export as fallback
  • OpenRouter — optional management API key (/credits + /activity), collected only when explicitly enabled with --openrouter. Tokens are last 30 days; all-time spend stays on the source object and is not rolled into the card's aggregate "compute spent"

It then shows you the exact JSON that would be uploaded — aggregate numbers only: token counts, cost totals, active days, streaks, model names. Never prompts, code, file paths, or project names. --dry-run uploads nothing at all.

On confirmation you get a permanent card URL like ai-era-card.vercel.app/s/mmi5GrqvJt that unfurls into a stats card when shared.

Options

--dry-run              build and print the payload, upload nothing
--json-out <file>      also write the payload to a local file
--yes / --force        skip prompts / skip upload confirmation
--openrouter           collect OpenRouter usage; prompts for a key if needed
--openrouter-key <k>   OpenRouter API key (or OPENROUTER_API_KEY env; requires --openrouter)
--cursor-cookie <t>    Cursor web session token (auto-detected if omitted)
--cursor-csv <path>    usage CSV export (fallback if the API path fails)
--no-claude-code / --no-codex / --no-cursor
--no-openrouter        legacy no-op (OpenRouter is already opt-in)
--handle <name>        display name on the card (unverified)
--no-baseline          don't save the local baseline file (see below)
--open                 open the card URL in your browser

Local baseline (deltas)

After a successful upload the CLI saves a small local file, ~/.aieracard/state.json, containing only the same aggregate numbers that are already public on your card (plus the date, schema version, and which sources were enabled). On your next run it uses that file to print "+240M tokens since your last card". The file never leaves your machine; delete it anytime, or pass --no-baseline to skip writing it.

Stats are self-reported, like any year-in-review.