For developers
Review, official badges and recommended plugins
What the team checks before publishing, where the Official and Recommended badges come from, how recommended plugins in the setup wizard work, and what happens when a plugin is suspended
On this page
What the team checks#
Every version of a plugin that runs code (JavaScript, WebAssembly / service, or templates with scripts and event handlers) is reviewed by the team before it is published. The team looks at:
- The code — it does what the README says, with nothing harmful or hidden
- The permissions asked for — only what is needed (e.g. no
content-writeif it only reads posts) - The domains called (
code.hosts/service.hosts) and any data sent off the site - Migrations — especially changes that could lose data
Outcomes: approved → published · not approved → rejected with a note (fix it and upload a higher version) · if a published version is withdrawn, it disappears from the store.
Ask for as few permissions as possible, and set minCore to the lowest system version the plugin really works on. Use feature detection for optional features of newer versions instead — see Plugin API.
Badges#
| Badge | Set by | Meaning |
|---|---|---|
| Official | The Anasaki team only (publishing with the operator token or as a store administrator), and the package must have "author": "Anasaki Studio" | A plugin the Anasaki Studio team maintains — it gets no special API rights over other plugins |
| Verified developer | Store administrators | Marked as verified by the store administrators |
| Recommended | Store administrators | On the Recommended plugins list of the CMS setup wizard |
Recommended plugins in the setup wizard#
The last step of Anasaki Studio's setup wizard is Recommended plugins. The CMS has no built-in list; it asks the Store:
- Only plugins that are both Recommended and Official are shown, in the order the store administrators set, then by name
- Store administrators decide which ones are ticked by default
- At install the CMS checks again that the plugin is still official and still recommended
- If the Store cannot be reached or recommends nothing, the wizard still finishes normally
So other developers' plugins don't appear in this step, but they can be found and installed as usual under Plugins → Plugin store.
When a plugin is suspended#
The team can suspend a problem plugin (e.g. after users report it with "Found a problem?"):
- The plugin is hidden from the store and cannot be downloaded
- No new versions can be uploaded until you contact the store administrators
- The plugin is added to the store's public advisory list (
GET /api/v1/advisories)
Testing with a local Store#
Every site connects to the official Store by default (there is no setting to change it). Developers who want to test against a Store running locally (e.g. http://localhost:8095) can set the STORE_URL variable for the CMS during development.
