Orca

Add your plugin

There is no form and no queue. Add a topic to your GitHub repository, push a version tag, and the directory lists it, usually within an hour, if it passes Orca's validator and the safety checks below. Your plugin's page, orca.dev/plugins/<owner>/<repo>, shows its status until then.

Publish your plugin

  1. 1Add the orca-plugin topic

  2. 2Push a vX.Y.Z tag

  3. 3Check your status page

    It shows whether the plugin is listed and, if not, exactly what to fix.

Step by step

  1. 1

    Write the plugin

    Put orca-plugin.json (manifest format 2) at the root of a public GitHub repository. Set publisher to your GitHub user or organization name, and add a license or a LICENSE file. See Writing an Orca plugin.
  2. 2

    Validate it

    From a checkout of Orca's repository, run the same check the directory runs:
    pnpm validate:plugin path/to/your-plugin
  3. 3

    Add the orca-plugin topic

    On GitHub: your repository → About (gear icon) → Topics. Or run:
    gh repo edit --add-topic orca-plugin
  4. 4

    Push a version tag

    The directory lists your newest vX.Y.Z tag, pinned to its exact commit and file hash. Pushes without a new tag change nothing.
    git tag v1.0.0 && git push origin v1.0.0

How plugins are labeled

Official

Reviewed and published by the Orca team in the official catalog. Shown with a check mark.

Community · unreviewed

Listed automatically. Checked by machine, not read by a person.

Full access

Runs its own code with your permissions. Shown on every card and page.

What gets a plugin left out

  • Orca's validator rejects the manifest or the release (manifest format 2 is required).
  • No license in orca-plugin.json or a LICENSE file GitHub can detect.
  • Binary files: executables, native modules, archives, symlinks. Images, including GIFs, and WOFF or WOFF2 web fonts are fine; TTF and OTF fonts are not.
  • A publisher that differs from the repository owner, imitates a reserved name (orca…, official, github and similar), or an id an official plugin already uses.
  • Forks, archived repositories and repositories with no version tag.
  • Anything on the takedown list.

Listing policy

Orca doesn't support paid plugins yet: no paywalls, license keys, trials or features locked behind payment. Connecting to a paid service the user already has is fine. No impersonating other brands, no malware, obfuscated code or tracking, and no explicit content in names or images. Read the full plugin listing policy.

Screenshots and covers

Add a cover (16:10, at least 800×500) and up to six screenshots (at least 1280×800) to your manifest. The directory copies them from your release; cards without a cover get drawn art from your theme colors or contribution type.

Takedowns and reports

Use “Report this plugin” on any plugin page. A plugin that is malicious, deceptive or infringing goes on the takedown list and disappears on the next run, and Orca's kill list disables copies that are already installed.