OpenPets LogoOpenPets
← Back to plugins
Community plugins

Build something great for the pet catalog

Have an idea for Spotify, calendar, focus, games, AI helpers, or tiny desktop rituals? Build it in a public GitHub repo, submit it for review, and we can list the safe, packaged version for every OpenPets user.

Open GitHub issue Start from template Read submit guide

Starter repo

Clone a complete example first

The starter repo includes a manifest, JavaScript entry, locale file, bundled SVG icon, README, and SDK smoke test. You can test it alone, then load that folder from OpenPets → Plugins → Developer Mode.

Open starter
1

Build the plugin

Create a manifest, one JavaScript entry file, locales, and any bundled assets.

2

Tag a release

Publish a GitHub tag or commit so reviewers can pin the exact source.

3

Get listed safely

OpenPets reviews permissions, hosts, assets, and packaging before it appears in the catalog.

What to prepare

  • A public GitHub repository with your plugin source.
  • A plugin folder containing openpets.plugin.json, index.js, locales/en.json, and declared assets.
  • A stable plugin id, semver version, minimal permissions, and exact network hosts.
  • A Git tag or full commit SHA that reviewers can pin.
  • A short README explaining what the plugin does and how users set it up.

Review packet

  • Plugin name and plugin id.
  • GitHub repo URL and plugin subdirectory.
  • Release tag or commit SHA.
  • Requested permissions and why each one is needed.
  • Network hosts and what each host is used for.
  • Any external account setup users need, such as OAuth app setup.

Copy into the GitHub issue if you are not using the form fields 

Plugin name:
Plugin id:
GitHub repo URL:
Plugin subdirectory: .
Release tag or commit SHA:

Requested permissions:
- permission-name: why it is needed

Network hosts:
- host.example.com: what it is used for

External account setup:
- None, or explain OAuth/API setup users must complete
Submit on GitHub
by Alvin