jasper-plugin-registry

Community plugin index for Jasper. The whole registry is one static file — no server:

https://raw.githubusercontent.com/jasper-note/jasper-plugin-registry/main/plugins.json

(raw.githubusercontent.com sends Access-Control-Allow-Origin: *, so the Jasper web UI can fetch the index and the .jplug artifacts directly from the browser and install them through the local host's existing install endpoint.)

Index format (schemaVersion: 1)

{
  "id": "s3-storage",            // == manifest id, ^[a-z0-9][a-z0-9-]*$
  "name": { "zh": "…", "en": "…" },         // display name, BOTH locales required
  "description": { "zh": "…", "en": "…" },  // both locales required
  "author": "…",
  "repo": "https://github.com/you/your-plugin",
  "version": "0.1.0",            // == manifest version
  "apiVersion": "0.2",           // == manifest apiVersion
  "minHostVersion": "",          // == manifest minHostVersion (empty = any)
  "capabilities": ["host:http"], // == manifest backend.capabilities, EXACTLY
  "download": "https://…/releases/download/v0.1.0/your-plugin-0.1.0.jplug",
  "sha256": "…"                  // sha256 of the .jplug artifact
}

Submitting a plugin

1. Build your plugin (start from jasper-plugin-template — its release CI produces the .jplug + .sha256 on a GitHub Release).
2. Open a PR adding one entry to plugins.json. name and description must be provided in both Chinese and English (the Jasper UI is bilingual and shows whichever matches the user's language) — machine translation is acceptable as a starting point; reviewers may polish it.
3. CI downloads your artifact and verifies: sha256, host size limit, and that the packaged manifest.toml agrees with your entry (id / version / apiVersion / capabilities must match exactly — the index is what reviewers and users see, it must not understate what the plugin can do).
4. Review: expect questions about every capability you declare — host:http means your plugin can talk to the network through the host, so say where it connects and why.

Version updates are the same: release on your repo, then PR the version / download / sha256 fields.

Trust model

Listing here means the entry is consistent and reviewed at the capability level — it is not a code audit. Plugins run sandboxed (wasm, no ambient IO; memory/CPU limits) and every capability requires explicit user consent at enable time. Treat host:http plugins with the same care as any software you give network access to.

License

Registry contents (index + scripts): MIT OR Apache-2.0.