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

deploy-forward

v0.12.2

Published

Deploy Forward tracker — ranks agentic engineers on what they ship. Measures your AI build time, tokens and outcomes locally (Claude Code; Codex next). Metadata only; never your code or prompts.

Readme

deploy-forward

The tracker for Deploy Forward — an agentic-engineering leaderboard that ranks the humans driving AI coding agents on tool-use effectiveness, not on how many tokens they burn.

Your Build Score is a composite of four axes — outcomes, efficiency, quality, consistency — where tokens and sessions live only in the efficiency denominator. Spending more can never raise your rank. Tokens, spend and sessions are tracked as status, never the ranking.

Board: https://deployforward-leaderboard.web.app

Get on the board

No install required — one command does everything (GitHub sign-in, scan, submit, profile URL):

npx deploy-forward

GitHub is the canonical identity: authentication is a browser device flow proven by OAuth — you never type a username, so identities can't be spoofed. Signing in on the web later with GitHub resolves to this same account (no duplicate).

Without an account, the local usage view still works:

npx deploy-forward usage

Commands

| Command | What it does | | --- | --- | | (bare) | GitHub sign-in, scan Claude Code + Codex, submit, print your profile URL. | | pair | Pair a second machine to your account (typed code; also Teams org enrollment). | | start | Live sync monitor (hooks already sync without it). | | sync | Sync once and exit. | | status | Show auth + how many transcripts are tracked. | | usage | Local per-model usage + session windows (--by-project, --by-day, --json, --cost). | | logout | Sign this device out (removes the device token). | | uninstall | Remove the Claude Code presence hooks. |

What it reads

Metadata only. The tracker reads token counts, timestamps, model names, and a local repo hash from your agent transcripts — never your code, prompts, or tool inputs. The repo hash is an HMAC computed locally with a key that never leaves your machine, so distinct repositories can be counted without any repo name or URL being sent.

Supported tools:

  • Claude Code~/.claude/projects/**/*.jsonl
  • Codex~/.codex/sessions/**/rollout-*.jsonl

Privacy & security

  • Device tokens: only a SHA-256 hash is ever persisted server-side.
  • GitHub verification is confirmed server-side; the badge can't be self-granted.
  • Local state lives in ~/.config/df/state.json (override with $DF_HOME).

MIT licensed.