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

@aidanhibbard/copse

v0.0.1

Published

Git worktree manager — create worktrees and open editors for parallel development

Readme

Copse

/käps/ - a small group of trees.

GitHub Actions Workflow Status NPM License NPM Downloads NPM Version NPM Unpacked Size

Git worktree manager — create worktrees and open editors for parallel development.

Work on multiple features simultaneously, each in its own editor window. No more stashing, no more branch switching.

Install

npm install -g @aidanhibbard/copse

Usage

Create a worktree

# Create a worktree for a branch and open it in Cursor
copse add feature/auth

# Use a different editor
copse add feature/api --editor code

# Custom path
copse add feature/dashboard --path ./dashboard-wt

# Create without opening an editor
copse add feature/tests --no-open

List worktrees

copse list

Open an existing worktree

# Open in Cursor (default)
copse open feature/auth

# Open in VS Code
copse open feature/auth --editor code

Remove a worktree

copse remove feature/auth

# Force remove
copse remove feature/auth --force

Supported Editors

| Editor | Flag value | | -------- | ---------- | | Cursor | cursor | | VS Code | code | | Zed | zed | | WebStorm | webstorm | | Neovim | nvim | | Vim | vim |

Any other value is treated as a command name — pass whatever editor CLI you have on your PATH.

How It Works

Copse wraps git worktree to manage worktrees as sibling directories:

projects/
├── my-repo/              # main worktree
├── my-repo-feature-auth/ # copse add feature/auth
├── my-repo-feature-api/  # copse add feature/api
└── my-repo-fix-bug/      # copse add fix/bug

Each worktree gets its own directory with a full working copy, and copse opens it in a separate editor instance so you can work on features in parallel.

License

MIT