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

v0.2.2

Published

Plugin manager for OpenCode. Search, install, and manage plugins without leaving your session.

Readme

opencode-lazy

npm CI Socket Badge

Plugin manager for OpenCode. Search, install, and manage plugins without leaving your session.

Inspired by lazy.nvim — you should never have to leave your editor to manage plugins.

How it works

The plugin registers a /plugin slash command and four tools via OpenCode's plugin hooks. When you run a command, the LLM calls the appropriate tool, which hits the npm registry and modifies your opencode.json directly. Config modifications use jsonc-parser to preserve any comments in your config files.

Installation

npm install -g opencode-lazy

Then add to the plugin array in your opencode.json:

{
  "plugin": ["opencode-lazy"]
}

Usage

/plugin search <query>     Search npm for OpenCode plugins
/plugin install <name>     Add a plugin to your config
/plugin list               Show all installed plugins
/plugin remove <name>      Remove a plugin from your config

Search for plugins

/plugin search auth

Searches the npm registry for packages prefixed with opencode- and returns matching results with name, version, and description. Supports scoped packages (@org/opencode-*).

Install a plugin

/plugin install opencode-wakatime

Validates the package on npm, adds it to your opencode.json plugin array. Restart OpenCode to activate.

By default, plugins are added to the global config (~/.config/opencode/opencode.json). The LLM can also install to the project config if you ask.

List installed plugins

/plugin list

Shows all plugins from both global and project configs.

Remove a plugin

/plugin remove opencode-wakatime

Removes the plugin from your config. Restart OpenCode to apply.

How it works (technical)

  • Registers a /plugin command via the config hook at startup
  • Registers four tools via the tool hook (plugin_search, plugin_install, plugin_list, plugin_remove)
  • Searches npm using the public registry API (registry.npmjs.org/-/v1/search)
  • Filters results to packages prefixed with opencode- or tagged with opencode-plugin
  • Modifies opencode.json using jsonc-parser to preserve comments and formatting
  • Supports both global (~/.config/opencode/) and project-level configs

Limitations

  • Restart required after install/remove — OpenCode doesn't support hot-reloading plugins
  • Token cost — Each /plugin command uses a small number of tokens since the LLM is in the loop
  • No version pinning — Always installs the latest version from npm

Disclaimer

This project is not built by the OpenCode team and is not affiliated with OpenCode in any way.

License

MIT