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

@dmandalik/cctower

v0.0.2

Published

Control tower for Claude Code - pre-flight token checks, attention alerts, and landing reports.

Readme

cctower

A turn auditor for Claude Code with a live status widget. After every turn, cctower reads the transcript and writes a "done ≠ correct" landing report: what changed, what was actually tested versus merely claimed, and a verdict — VERIFIED · UNVERIFIED · FAILED · NO-OP. If Claude says "tests pass" but never ran them, the card says so.

Local only: no API keys, no accounts, no network calls. cctower attaches through Claude Code's lifecycle hooks and statusline, never intercepts or slows a session, and fails open on any internal error.

What you get

  • Landing reports — per-turn markdown cards with files touched, git diff stats, test/build runs and exit codes, new TODO/FIXMEs, claims checked against reality, and a verdict.
  • Live widget (cctower ui) — a compact local panel: per-session status orbs (working · needs input · issue · done), an alert bar + title flash when any chat needs you, the latest landing cards, the last pre-flight readout, and controls (mode, alerts, thresholds, per-project mute).
  • Stall watcher — Claude Code fires no hook while a permission or question dialog is open, so the gate keeps a tiny detached watcher process alive (auto-spawned per prompt, self-exits after 10 idle minutes). It tells a blocked tool apart from a running one via the process table, so a slow command never reads as "needs input".
  • Pre-flight gate — estimates each prompt's token cost, projects context use, lints weak prompts, and can block (gate mode, !force to override). Self-tunes against real usage.
  • Best-effort extras — desktop notifications and quota readouts, with platform limits stated plainly below.

Install

npm install -g @dmandalik/cctower
cctower init --dry-run
cctower init

(The package is scoped; the installed command is still plain cctower.)

init merges cctower's entries into ~/.claude/settings.json idempotently — running it twice changes nothing, and your own hooks are left untouched. The previous file is backed up under ~/.cctower/backups/ first. --dry-run prints the exact diff and touches nothing.

Commands

cctower status       # state-dir + install health, estimator accuracy
cctower ui           # live widget (sessions, cards, controls)
cctower report       # 7-day summary: verdicts, idle time, top lint findings
cctower uninstall    # remove only cctower's entries; prints the newest backup

Modes

Set mode in ~/.cctower/config.json or from the widget:

  • observe — log only.
  • advise (default) — pre-flight hints on each prompt; silent on trivial prompts. In GUI clients the hint arrives as a desktop notification (hook stdout only reaches the model), plus the widget's pre-flight row.
  • gate — block a prompt when projected context/quota crosses a threshold; resend with !force in the prompt to override.

Note: in GUI clients (desktop app, IDE) the pre-flight advise line is injected into the model's context but not shown to you — the widget's "last pre-flight" row and the statusline are the user-facing surfaces.

Known platform limits

  • macOS may suppress scripted notification banners. cctower posts via terminal-notifier when you've installed it (optional, auto-detected — not a dependency), else via osascript (shows as "Script Editor"). For banners: System Settings → Notifications → allow the posting app and set its style to Alerts or Banners; check that no Focus mode is active. Even then, recent macOS versions sometimes deliver scripted notifications silently to Notification Center. The widget and its sound ping are the reliable surface.
  • Quota is best-effort. Claude Code only exposes rate_limits to the statusline on some versions. When present, cctower shows official percentages; when absent, it shows token volume aggregated from your local transcripts over rolling 5-hour/7-day windows, tagged "local estimate" (no percentage — plan limits aren't knowable locally).
  • Claude Code only. cctower attaches via local hooks, so it covers the CLI, desktop app, and IDE sessions — not claude.ai web chats, which run no local hooks.

State

Everything lives under $CCTOWER_HOME (default ~/.cctower/). Set CCTOWER_HOME to relocate or isolate it — the whole tool is contained there.

License

MIT