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

@alejandroroman/cc-statusline

v1.1.0

Published

A rich Claude Code status line with model info, context usage, native rate limit data, and an interactive installer.

Readme

claude-statusline

npm version npm downloads License: MIT

A rich multi-line status line for Claude Code using Claude Code's native status line data.

status line screenshot

What it shows

| Line | Content | Source | |------|---------|--------| | 1 | Model name, token counts, used/remaining %, lines changed | Real data from Claude Code | | 2 | Context bar, 5-hour usage bar, weekly usage bar | Real data from Claude Code status line JSON | | 3 | Rate limit reset times | Real reset times from Claude Code status line JSON |

How it works

Claude Code pipes a JSON object to the status line command via stdin on each render tick. The script:

  1. Extracts token counts and context data from stdin JSON (single jq call)
  2. Reads rate_limits.five_hour and rate_limits.seven_day when Claude Code provides them
  3. Formats everything with ANSI colors and dynamic color-coding (green/yellow/red based on usage level)

Rate limit bars show --- before Claude Code has emitted rate limit fields, or for plans/accounts where those fields are not available.

Requirements

  • Node.js 18+ (for the installer wizard)
  • jqbrew install jq (macOS) or apt install jq (Linux)
  • Claude Code CLI

Note: Claude Code exposes context and rate limit fields through the official statusLine stdin JSON. Context fields are available after the first API response. Rate limit fields appear for Claude.ai subscribers when Claude Code provides them; API/pay-per-token users may see --- for those bars.

Install

npx @alejandroroman/cc-statusline

Or clone and run locally:

git clone https://github.com/aromanarguello/claude-statusline.git
cd claude-statusline
./install.sh

The wizard asks what data to show, how to format it, previews the result, then writes the script and patches ~/.claude/settings.json (only the statusLine key — all other settings preserved).

Using the wizard

Running npx @alejandroroman/cc-statusline (or node setup.js if cloned locally) walks you through 4 steps:

Step 1 — Pick your fields (multi-select, space to toggle)

◆ Which data fields do you want?
◇ ◼ Model name
◇ ◼ Token counts (used / total)
◇ ◼ Used % with raw token count
◇ ◼ Remaining % with raw token count
◇ ◼ Lines changed (+added / -removed)
◇ ◼ Context window progress bar
◇ ◼ 5-hour & weekly rate limit bars
◇ ◼ Rate limit reset times

Step 2 — Pick a layout

◆ Layout?
● Multi-line  (model/tokens on line 1, bars on line 2)
○ Single line (everything on one line)

Step 3 — Pick colors

◆ Color style?
● Traffic-light  (green <50%, yellow 50-79%, red >=80%)
○ Monochrome  (no colors)
○ Custom thresholds

Step 4 — Preview + confirm

The wizard renders your statusline with sample data so you see exactly what it looks like before writing anything:

Claude Sonnet 4.6 (1M context) | 48k / 1000k | 5% used 48,200 | 95% remain 951,800
context: ○○○○○○○○○○ 5% | 5-hour: ●●○○○○○○○○ 23% | weekly: ●●●●○○○○○○ 41%
5-hour resets 11:00am feb 01 | weekly resets 11:00am feb 06

Then confirms before touching any files:

◆ Write to ~/.claude/statusline-command.sh and patch settings.json? Yes

After confirming, restart Claude Code to see your new status line.

What you can configure

| Field | Description | Requires | |-------|-------------|---------| | Model name | Active Claude model | — | | Token counts | Used / total context size | — | | Used % | % of context used | — | | Remaining % | % of context remaining | — | | Lines changed | +added / -removed in session | — | | Context bar | ●●●○○○○○○○ visual progress bar | — | | Rate limit bars | 5-hour & weekly usage bars | Claude Code rate_limits fields | | Reset times | When rate limits reset | Claude Code rate_limits fields |

Enterprise/API users: Rate limit fields degrade gracefully to --- when Claude Code does not provide usage caps. The context bar and session stats still work.

Reconfigure

npx @alejandroroman/cc-statusline

Re-running the wizard overwrites ~/.claude/statusline-command.sh with your new choices.

Uninstall

cd claude-statusline && ./uninstall.sh

License

MIT