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

@trquth/base-claude-statusline

v1.0.5

Published

A compact status line for [Claude Code](https://claude.com/claude-code).

Readme

🌿 base-claude-statusline

A compact status line for Claude Code.

Claude Code status line

It shows, on one line:

📁 my-project | ⎇ main | 🤖 Opus [high] | 🌿 ctx: 42% | 🕐 5h: 55% (50m) | 📅 7d: 72% (Tue 09:00 AM)

| Segment | Meaning | | ---------- | ------------------------------------------------------------------ | | 📁 | Current directory name | | ⎇ | Git branch | | 🤖 | Model name, plus the effort level when it isn't medium | | 🌿 ctx | Context window used (white under 50%, yellow under 75%, red above) | | 🕐 5h | 5-hour rate limit used, with time until reset | | 📅 7d | 7-day rate limit used, with the reset day and time |

Segments whose data isn't available are left out.

📋 Requirements

  • 🐚 bash
  • 🔧 jq (brew install jq or apt install jq)
  • 📦 Node.js, for the npx installer
  • 🔀 git, for the branch segment

🍎 🐧 Works on macOS and Linux.

🚀 Install

💡 Pick one method. Both set the status line up for a single project. Restart Claude Code (or start a new session) afterwards to see it.

⚡ Option 1: Automatic (npx)

  1. Make sure Node.js and jq are installed.

  2. Open a terminal in the project where you want the status line.

  3. Run:

    npx @trquth/base-claude-statusline

    The installer copies the script to .claude/statusline.sh, sets statusLine in .claude/settings.json (keeping your other settings) and warns if jq is missing. Before changing settings.json it asks a Yes/No question (default Yes); answer No to copy only the script and wire it up yourself. Add --yes (or -y) to skip the question; it is also skipped when the input is not a terminal.

  4. Restart Claude Code.

If .claude/settings.json already has a different statusLine, the installer leaves it alone. To replace it, add --force:

npx @trquth/base-claude-statusline --force

To update later, run npx @trquth/base-claude-statusline@latest. From a clone, npx /path/to/base-claude-statusline works too.

🛠️ Option 2: Manual

  1. Make sure bash and jq are installed.

  2. Get scripts/statusline.sh from this repo (clone it, or download that one file).

  3. From your project root, copy it into place and make it executable:

    mkdir -p .claude
    cp /path/to/base-claude-statusline/scripts/statusline.sh .claude/statusline.sh
    chmod +x .claude/statusline.sh
  4. Open .claude/settings.json, creating it if it doesn't exist, and add the statusLine entry. Keep any settings already in the file:

    {
      "statusLine": {
        "type": "command",
        "command": "bash \"$CLAUDE_PROJECT_DIR\"/.claude/statusline.sh"
      }
    }
  5. Restart Claude Code.

🗑️ Uninstall

From the same project, run:

npx @trquth/base-claude-statusline --uninstall

This deletes .claude/statusline.sh and removes statusLine from .claude/settings.json, keeping your other settings. It deletes settings.json and .claude/ only if they end up empty. If statusLine was set to something other than this status line, it is left alone; add --force to remove it anyway.

To undo it by hand, delete .claude/statusline.sh and remove the statusLine entry from .claude/settings.json.

🧪 Try it without installing

Pipe sample JSON into the script:

echo '{"cwd":"'"$PWD"'","model":{"display_name":"Opus"},"context_window":{"used_percentage":42}}' | bash scripts/statusline.sh