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

codex-usage-profile

v0.1.4

Published

Connect local Codex usage to a Codex Usage Profile.

Vulnerabilities

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

Links

Git

Maintainers

postmeleepostmelee

Keywords

codexopenaiusageprofilegithub-readme

Readme

codex-usage-profile

Submit the account usage shown by Codex to your GitHub-backed Codex Usage Profile and receive stable profile, card, and README links.

Quick start

Run this on the machine where Codex is signed in:

npx codex-usage-profile@latest submit

If a service credential is not stored yet or is no longer valid, submit guides you through browser approval and continues in the same terminal after approval. npm may first ask you to confirm the package and version before installation.

After submission:

  1. Review your private card preview on the website.
  2. Select Publish card when you are ready.
  3. Copy the README Markdown or open a social sharing action from Share.

Interactive runs may optionally ask whether you want to star the project. Declining does not affect submission, and the prompt is skipped in CI and non-interactive runs.

Requirements

  • Node.js 20 or newer
  • A recent codex CLI on PATH, or on macOS a standard ChatGPT.app or Codex.app installation
  • A ChatGPT-backed Codex sign-in that supports account/usage/read
  • A GitHub account connected through the Codex Usage Profile website

API-key-only and Bedrock authentication do not provide the account usage method used by this CLI.

Commands

| Command | What it does | |---|---| | npx codex-usage-profile@latest submit | Sign in through browser approval when needed, then read and submit current Codex usage | | npx codex-usage-profile@latest login | Check the saved service login and start browser approval when needed | | npx codex-usage-profile@latest status | Show the connected account and latest submission metadata | | npx codex-usage-profile@latest logout | Remove the locally stored service credential | | npx codex-usage-profile@latest --help (-h) | Show all commands; add --help after a command for its supported options | | npx codex-usage-profile@latest --version (-v) | Show the installed CLI version |

logout removes only the local credential file. Revoke the server token from web Settings when a machine is no longer trusted.

An account can have up to three active CLI/API tokens. If the limit is reached, revoke an older Device login token in web Settings, then retry with a new code.

Submit result

A successful interactive submit returns copyable profile, card, and README values:

✓ Usage submitted successfully.
Captured: 2026-07-11T00:00:00.000Z

Links
  Profile: https://codex-usage-profile.meleeisdeveloping.chatgpt.site/?view=profile
  Card:    https://codex-usage-profile.meleeisdeveloping.chatgpt.site/u/octocat/card.png
  README:  <a href="https://codex-usage-profile.meleeisdeveloping.chatgpt.site/api/share/octocat"><img width="50%" src="https://codex-usage-profile.meleeisdeveloping.chatgpt.site/u/octocat/card.png" alt="Codex usage profile" /></a>

Supported interactive terminals show the Profile and Card URLs as clickable links. The README value remains exact plain HTML so it can be copied without terminal control sequences.

The README link and image source stay fixed after future submits. The website uses revisioned links for new social posts without changing this Markdown.

What submit sends

The CLI sends one Account Usage Contract v1 document containing:

  • contract version and capture time
  • lifetime and peak daily tokens
  • longest-running turn and streak counts
  • source-dated daily token buckets

It does not send Codex/OpenAI credentials, GitHub OAuth credentials, prompts, responses, tool data, local session files, or filesystem paths. GitHub identity and profile visibility remain server-owned.

Credentials and automation

Browser approval stores a narrow service credential in the operating system's user configuration directory. On macOS and Linux, the directory and file use owner-only permissions. logout removes the local file; it does not revoke the server token or unset an environment-provided token.

For trusted non-interactive automation, inject a pre-issued token through a secret manager, pin the CLI to an exact version, and request JSON output:

CODEX_USAGE_PROFILE_TOKEN='<service-submit-token>' \
npx --yes [email protected] submit --json

Do not put the token in command arguments, URLs, repository variables, logs, or shell history.

Documentation

License

MIT. This independent community project is not affiliated with, endorsed by, or sponsored by OpenAI. OpenAI and Codex names and trademarks belong to their respective owners.