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

opencode-worktree-tools

v0.1.0

Published

OpenCode plugin: git worktree tools for the agent, in the same place Claude Code puts worktrees. No terminals, no prompt injection.

Readme

opencode-worktree-tools

Gives the agent three tools to make, list and remove git worktrees, so parallel or risky work happens in its own checkout instead of your working tree. It's the OpenCode counterpart of Claude Code's worktrees, and it puts them in the same place: <repo>/.claude/worktrees/<name>.

It stays out of the way:

  • Tools only. Nothing is added to the system prompt, so the model reaches for a worktree when isolation actually helps, not on every task.
  • No new terminals or sessions. The session keeps running where it is and works in the worktree by using its absolute path as the shell workdir and in file paths.
  • Your repo isn't edited. .claude/worktrees/ is ignored through .git/info/exclude, not .gitignore.
  • Nothing is lost on cleanup. Removing a worktree refuses when it has uncommitted changes (unless force is set), and its branch is only deleted when it's fully merged.

Tools

| Tool | What it does | | ----------------- | ------------------------------------------------------------------------------------------------ | | worktree_create | Creates .claude/worktrees/<name> on branch <name>, from the current HEAD or a given base. | | worktree_list | Lists those worktrees with their branch and whether they have uncommitted changes. | | worktree_remove | Removes one, and deletes its branch only if it's merged. |

Dependencies such as node_modules aren't copied into a new worktree; the agent is told to install them there if needed.

Install

opencode plugin opencode-worktree-tools -g

Drop -g for the current project only. Restart OpenCode afterwards; plugins load at startup.

Without npm

mkdir -p ~/.config/opencode/plugins
curl -fsSL https://raw.githubusercontent.com/moritzWa/opencode-worktree-tools/main/index.js \
  -o ~/.config/opencode/plugins/worktree-tools.js

Files in ~/.config/opencode/plugins/ load automatically. The plugin imports @opencode-ai/plugin, which OpenCode installs into that config folder.

License

MIT