Skip to content
    ↑↓ select↵ openesc close
    English中文

    Submit a plugin

    Good news: there is nothing to submit.Publish to npm with the right keyword and you are listed the next day.

    1. 01

      Publish to npm

      The plugin has to be a public npm package. Private packages, and repositories that only exist on GitHub, cannot be discovered automatically.

    2. 02

      Add the opencode-plugin keyword

      Put opencode-plugin in the keywords array of your package.json. That is the only listing requirement, and the entry point for the whole crawler.

      package.json
      {
  "name": "opencode-your-plugin",
  "description": "One line on the problem it solves",
  "keywords": ["opencode", "opencode-plugin"],
  "repository": "github:you/your-plugin",
  "license": "MIT"
}
    3. 03

      Fill in the metadata

      Description, repository, licence, README — those four decide your health badges and your search ranking. Each one missing adds a warning flag.

    4. 04

      Wait a day

      The crawl runs once daily. Your plugin appears the day after you publish. No pull request, no form.

    Wrong data? Wrong category?

    Automatic categorisation gets things wrong, and star counts read high for packages living inside a monorepo. Both are fixable through a manual override layer \u2014 open an issue with the package name and what should change.

    Open a correction issueHow ranking works

    Want to be removed?

    Drop the opencode-pluginkeyword from your package.json, or open an issue asking to be blocklisted. Either way the next crawl removes it.