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-plugin-updater

v1.0.12

Published

Auto-update plugin for OpenCode - reads plugins.json and keeps plugin repos up to date

Downloads

1,285

Readme

opencode-plugin-updater

npm version npm downloads CI License: MIT

Auto-update plugin for OpenCode.

Reads config/plugins.json, clones/pulls each plugin repo, runs configured build steps, and copies the output to the plugin directory on every OpenCode startup.

Features

  • Automatic updates on startup — pulls latest code and rebuilds changed plugins in the background
  • Manual mode — disable auto-update per plugin; update on demand via the plugin_update tool
  • <creator>/<repo> directory layout — repos are stored under repos/<github-user>/<repo-name>, preventing name collisions
  • Initial clone for manual plugins — even plugins with autoUpdate: false are cloned on first run so they are available immediately
  • Centralized config — reads/writes config/plugins.json (auto-migrates from the legacy root location)
  • Centralized logs — writes to logs/plugin-updater.log with automatic log rotation (keeps last 100 lines)
  • Dual-exec guard — prevents running twice when OpenCode loads the plugin file more than once

Installation

Option A — npm (recommended)

Add the package to your ~/.config/opencode/opencode.json:

{
  "plugins": ["opencode-plugin-updater@latest"]
}

Restart OpenCode. The plugin is loaded directly from npm — no cloning or building required.

Option B — Manual bootstrap

  1. Clone the repo:
mkdir -p ~/.config/opencode/repos/intisy/opencode-plugin-updater
git clone https://github.com/intisy/opencode-plugin-updater.git ~/.config/opencode/repos/intisy/opencode-plugin-updater
cp ~/.config/opencode/repos/intisy/opencode-plugin-updater/plugin-updater.js ~/.config/opencode/plugins/plugin-updater.js
  1. Register the plugin in ~/.config/opencode/opencode.json:
{
  "plugins": {
    "plugin-updater": "./plugins/plugin-updater.js"
  }
}

Restart OpenCode. The plugin will keep itself (and all other plugins) up to date automatically from then on.

plugins.json Format

Create ~/.config/opencode/config/plugins.json with an array of plugin entries:

[
  {
    "name": "my-plugin",
    "url": "https://github.com/user/my-plugin.git",
    "install": ["bun", "install"],
    "build": ["bun", "run", "build"],
    "bundle": null,
    "output": "dist/plugin.js",
    "pluginFile": "my-plugin.js",
    "autoUpdate": true
  }
]

| Field | Type | Description | |-------|------|-------------| | name | string | Plugin identifier (used as repo folder name) | | branch | string | null | Git branch to clone/pull (defaults to default branch) | | url | string | Git clone URL | | install | string[] | null | Install command (e.g. ["bun", "install"]) | | build | string[] | null | Build command (e.g. ["bun", "run", "build"]) | | bundle | string[] | null | Bundle command (optional second build step) | | output | string | Path to the built plugin file inside the repo | | pluginFile | string | Filename to use in the plugins/ directory | | autoUpdate | boolean | Whether to auto-update on startup |

Tools

| Tool | Description | |------|-------------| | plugin_list | List all managed plugins with status, commit, and update availability | | plugin_update | Pull, rebuild, and deploy a single plugin (or all) | | plugin_auto_update | Toggle auto-update for a specific plugin |

License

MIT