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

@kym6464/claude-state

v0.1.5

Published

A lightweight CLI for managing session-scoped state in Claude Code hooks

Readme

claude-state

A lightweight CLI for managing session-scoped state in Claude Code hooks.

Why

Claude Code hooks often need to track state across a session (e.g., "only nudge once", "remember if lint errors were pre-existing"). Without a shared mechanism, each hook invents its own marker files, polluting /tmp and duplicating logic.

claude-state provides a single key-value store per session, scoped automatically by session_id.

Installation

brew install kym6464/tap/claude-state

Usage

claude-state [--session-id <id>] <command> <key> [value]

Commands

| Command | Description | Exit code | | ----------------- | ------------------------- | ---------------------- | | has | Check if a key exists | 0 if set, 1 if not | | get | Print the value of a key | 1 if not set | | set | Set a flag (boolean true) | | | set | Set a key to a value | | | delete | Remove a key | | | list | Print all key-value pairs | |

Session ID

By default, claude-state reads the hook's JSON input from stdin to extract session_id. This means in the simple case you don't need to pass anything — just pipe stdin through.

If your hook needs stdin for other purposes, pass the session ID explicitly:

claude-state --session-id <id> <command> <key> [value]

Storage

State is stored in ${TMPDIR:-/tmp}/claude-state/<session_id>.json. Each session gets its own file, automatically created on first write.

Examples

Simple hook — only fire once per session

A PostToolUse hook that provides feedback to Claude, but only the first time:

#!/bin/bash
claude-state has migration_warning_sent && exit 0
claude-state set migration_warning_sent
cat <<'EOF'
{
  "hookSpecificOutput": {
    "hookEventName": "PostToolUse",
    "additionalContext": "This project uses v2 of the config format. See docs/migration.md before making changes."
  }
}
EOF

Hook that also reads stdin

When your hook needs to inspect the tool input/output in addition to managing state, capture stdin first and pass the session ID explicitly:

#!/bin/bash
INPUT=$(cat)
SESSION_ID=$(echo "$INPUT" | jq -r '.session_id')

claude-state --session-id "$SESSION_ID" has deprecation_warning_sent && exit 0

if echo "$INPUT" | grep -q 'legacyApi'; then
  claude-state --session-id "$SESSION_ID" set deprecation_warning_sent
  # ... output nudge JSON
fi