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

claude-highlight

v1.0.3

Published

Colors epistemic markers in Claude Code's output, live, in the terminal

Readme

claude-highlight

alt text

Colors the hedges in Claude Code's output, live, as it streams.

Words like likely, seems, assuming, untested and obviously get a color so you can see at a glance where the model is guessing, admitting a gap, or overclaiming. Nothing else about the session changes.

Install

npm install -g claude-highlight
bun install -g claude-highlight

Use

claude-highlight              # instead of: claude
claude-highlight --resume     # any claude arguments pass straight through

Press F9 during a session to toggle categories. Changes apply immediately and are saved.

Scripts and hooks still get the real claude.

claude-highlight --hl-selftest   # prints sample text; check that color shows up
claude-highlight --hl-help       # the wrapper's own flags

What gets colored

| category | examples | default | |---|---|---| | inference | likely, probably | on | | unknown | untested, can't verify | on | | assumption | assuming, in theory | on | | appearance | seems, looks like | on | | overclaim | obviously, clearly | on | | modal | might, could be | off | | vagueness | roughly, several | off | | softener | a bit, fairly | off |

Only Claude's prose is colored. Your own messages, inline code, and fenced code with a language tag are left alone. A fenced block with no language looks like prose in the byte stream, so hedge words inside one are still colored.

Config

~/.config/claude-highlight/config.json (honors XDG_CONFIG_HOME), re-read whenever it changes. Add words to a category, or define your own:

{
  "categories": {
    "inference": { "add": ["gut feel", "ballpark"] }
  },
  "custom": {
    "deadline": {
      "color": "38;5;99", "on": true, "desc": "schedule risk",
      "terms": ["slipping", "at risk", "behind schedule"]
    }
  }
}

Terms are matched literally; prefix with re: for a regex. Terms that fail to compile are skipped and listed by --hl-selftest.

How it works

It runs claude on a pseudo-terminal and wraps matched words in ANSI color codes on the way to your screen. Color codes are zero-width, so Claude Code's layout is unaffected. A filter keeps matches out of escape sequences and handles words split across stream chunks; a shadow screen removes color that would otherwise linger after Claude redraws a line, and keeps color out of the input box while you type.

Development

git clone https://github.com/NoahBPeterson/claude-highlight
npm run test:all      # every suite, under node
npm run test:all:bun  # same suites, under bun
bun run build         # dist/, what the published bin points at

Building needs Bun, but running does not. The pty comes from node-pty under Node and from openpty via bun:ffi under Bun. Everything else is shared.

The repo also contains src/hedge_scan.ts, which scores your local Claude Code transcripts with the same lexicon, and src/hedge_hook.ts, a Stop hook that flags hedge-heavy turns. Neither is part of the npm package.

License

MIT