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-jump

v1.0.1

Published

Jump to any project (interactive menu, ranked by frecency) and launch Claude Code in one command.

Readme

claude-jump

Jump to any project (interactive menu, ranked by how often/recently you use it) and launch Claude Code in one command — instead of cd-ing there by hand every time.

Built on zoxide (recent/frequent directory tracking) and fzf (fuzzy interactive menu).

Install

npm i -g claude-jump
# or
pnpm add -g claude-jump
# or
bun add -g claude-jump

This installs the cj, cj-scan and cj-setup commands globally, and runs a setup step that installs fzf and zoxide if missing (via Homebrew / apt / dnf / pacman) and adds the zoxide shell hook to your rc file (zsh or bash).

pnpm and bun block install scripts by default for security, so the setup step may not run automatically. If cj doesn't work after install, run the setup manually:

cj-setup

Then restart your terminal, or run source ~/.zshrc (or ~/.bashrc).

Usage

cj              # interactive menu of your projects, launches Claude Code in the one you pick
cj myproject    # jump straight to the best match for "myproject", no menu

The project list starts empty and fills up naturally as you cd around (that's what zoxide tracks). To seed it immediately with your existing projects:

cj-scan ~/Desktop ~/Documents   # finds every git repo under these paths and adds it to the list
cj-scan                         # defaults to scanning the current directory

Uninstall

npm uninstall -g claude-jump
# or
pnpm remove -g claude-jump
# or
bun remove -g claude-jump

This removes the cj, cj-scan and cj-setup commands and the zoxide hook block from your shell rc file. fzf and zoxide themselves are left installed since other tools may use them.

How it works

  • zoxide maintains a frecency-ranked (frequency + recency) database of directories you visit.
  • cj opens that list through fzf for a fuzzy interactive pick, then launches claude in that directory.
  • cj <name> skips the menu and jumps to zoxide's best match directly.
  • cj is a real binary (bin/cj.js), so quitting Claude Code leaves you back where you started — it doesn't persist a cd in your shell.

License

MIT