Valid plugin.json manifest with key, name, version, and description fields.
At least one service or widget bundle declared in the manifest — a plugin can ship services only, widgets only, or both.
Plugin packaged as a .zip archive.
No malicious or obfuscated code — submissions are reviewed before approval.

Review process

Submissions go through a manual review before appearing in the public registry. Rejected submissions include a reason so you can address the issue and resubmit. After submitting, you will receive a submission ID — use it to check your review status at any time on the submissions page.

Ownership token

When you submit a plugin for the first time, the registry issues an ownership token tied to your plugin's key. This token is shown once immediately after submission and is never stored or displayed again — copy it somewhere safe before leaving the page.

Every time you submit an update to the same plugin key, you must include this token. It is the only proof that you are the original author. Submissions that provide an incorrect or missing token for an existing plugin key will be rejected.

There is no account system and no recovery mechanism — if you lose the token, you will not be able to publish updates under that plugin key.

Ready to submit?

Use the submission form to upload your plugin zip. No account or contact details are required — keep your submission ID safe, as it is the only way to look up your review status.

Go to the submission form →