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

@supersession/sup

v0.1.9

Published

Your AI coding session, superseded — hand it off to any tool and keep going.

Readme

Supersession

Your AI coding session, superseded — hand it off to any tool and keep going.

Hit your Claude Code limit mid-task? Switching machines? Handing work to a teammate? sup reads your current session, distills it into a repo-grounded continuation brief, and writes it in the format the next tool expects — so the new agent continues instead of restarting.

npm i -g @supersession/sup

# wire it into every AI tool on your machine (Claude Desktop/Code, Cursor,
# Codex, Windsurf, VS Code, Antigravity) — drive it from inside them, no terminal:
sup install      # Claude Code gets /sup-refresh + /sup-handoff; elsewhere just ask

# your long session got dumb (context rot)? start fresh WITHOUT losing the arc:
sup status       # session health: size + rot signals
sup refresh      # fresh window, full arc — distills the complete on-disk
                 # transcript, not the degraded live window like /compact

# hit your Claude Code limit mid-task? continue in another tool:
sup codex        # writes AGENTS.md; Codex picks up where Claude left off
sup preview codex   # see the exact brief first — writes nothing

# plan on your phone in ChatGPT, build on your machine:
sup import chat.json claude

sup list         # what session sup sees for this directory

How it works

discover → parse → redact → distill → write
  1. discover — find the current directory's latest session
  2. parse — into the Neutral Session Format (NSF), a tool-agnostic shape
  3. redact — strip API keys / secrets locally before anything moves
  4. distill — a continuation brief: goal, files touched (checked against the live repo), commands run, recent turns verbatim, next step
  5. write — the target tool's native kickoff file (AGENTS.md, CLAUDE.local.md, GEMINI.md)

Every handoff prints a fidelity report: what carried verbatim, what was summarized, what was dropped, how many secrets were redacted. Lossy on purpose, never silently.

Status

v0.1 — local handoff engine + cloud vault. Source parsers (verified): Claude Code, Codex CLI, Cursor — sup reads whichever you worked in last. Targets: Claude Code, Codex, Cursor, Gemini, Antigravity. Sessions carry a title + summary and version on re-push (v1, v2, …), browsable in the web dashboard. sup facts surfaces the credentials/URLs a session generated, locally. Web-chat import and teams are on the roadmap (see SPEC.md).

Develop

pnpm install
pnpm test        # unit tests with a schema-faithful fixture
pnpm build       # tsc -> dist/
pnpm dev list    # run the CLI from source

MIT.