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

coding-plan-comparison

v0.2.1

Published

CLI to collect AI coding tool usage data for plan comparison

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

vivaxyvivaxy

Keywords

aicodingclaudecursorcopilotusagecli

Readme

coding-plan-comparison

CLI to collect AI coding tool usage data from your local machine and export it for plan comparison.

Usage

# Collect all detected tools, print summary + JSON
npx coding-plan-comparison

# Output JSON only (for piping or redirect)
npx coding-plan-comparison --json

# Copy JSON to clipboard (macOS)
npx coding-plan-comparison --copy

# Limit to a date range
npx coding-plan-comparison --since 2026-03-01 --until 2026-04-22

# Only specific tools
npx coding-plan-comparison --tools claude-code,codex

Adapter coverage

| Tool | Verdict | Data available | |---|---|---| | Claude Code | Rich | Tokens (4 kinds), sessions, messages, model breakdown | | Codex CLI | Partial→Rich | Sessions, messages; tokens if sqlite present | | Cursor | Minimal | Conversation count; quota is manual (in-app dashboard) | | Windsurf | Minimal | Conversation count; quota is manual | | GitHub Copilot | Manual | No local data — follow guidance URL | | Gemini CLI | Manual | No local data — follow guidance URL |

Privacy

Everything runs locally. No data is sent anywhere. The JSON output contains only aggregated usage counts from files already on your machine.

Releasing

Releases are automated via semantic-release. Merging a Conventional Commit to main triggers a release if the changes are releasable:

| Commit prefix | Version bump | |---|---| | fix: / fix(cli): | patch | | feat: / feat(cli): | minor | | BREAKING CHANGE: footer | major |

Tag format: cli-vX.Y.Z. The workflow publishes to npm with OIDC provenance and creates a GitHub Release automatically.

One-time setup

  1. Claim the package name on npm — npm login && npm publish --access public from this directory to create the package before CI takes over.
  2. Configure Trusted Publishing on npmjs.com — package settings → "Automated Publishing" → add GitHub Actions publisher for vivaxy/coding-plan-comparison, workflow release-cli.yml. No NPM_TOKEN secret is needed after this.
  3. Tag the initial version — before the first automated release, tag the current commit so semantic-release starts from the right base:
    git tag cli-v0.1.0 && git push origin cli-v0.1.0