# Anasaki Plugin Store overview

> The Plugin Store is the official plugin store of Anasaki Studio — search, review the permissions, install in one click and publish plugins of your own

Source: https://anasaki.live/docs/en/store/store-overview

The **Anasaki Plugin Store** ([storecms.anasaki.live](https://storecms.anasaki.live)) is the official plugin store of Anasaki Studio. It has two parts:

- **The store website** — browse plugins by category, see the rankings (trending this week, top rated, most downloaded), read details, screenshots, version history, reviews and the permissions a plugin uses, download the `.zip`, and the **Developers** page for publishing plugins
- **An API** every Anasaki Studio site uses to install plugins from the admin (**Plugins → Plugin store**)

Every site connects to the official Store automatically; nothing to set up (developers testing against a local store use the `STORE_URL` variable).

## Kinds of plugins

| Kind | What it is | Install |
| --- | --- | --- |
| **Package (static)** | A `.zip` with `manifest.json`, templates and CSS/JS — adds designer blocks, a settings page and webhooks. No server-side code, so it cannot reach the site's database or files | One click |
| **JavaScript** | TypeScript/JavaScript the CMS runs in the Site Code engine as a separate unit, with its own tables, routes, settings and cookies — limited to the code permissions it declares | One click |
| **WebAssembly** | Server-side code (`plugin.wasm`) the CMS runs in a sandbox — it can only call the APIs it declares | One click |
| **External service** | A separate program the site owner runs (e.g. in Docker) and connects on the plugin's settings page | Run the container yourself |

The official plugins are JavaScript plugins. See [Official plugins](/docs/en/store/official-plugins).

## Plugin safety

- Every package is checked automatically before it reaches the store (size, file types, paths and the manifest)
- Plugins that **run code** (JavaScript, WebAssembly, services or templates with scripts) are reviewed by the team before every version is published
- Every package is **signed** by the store, and sites check the signature before installing (CMS 2.4.0), so a package changed on the way is refused
- Before installing, the admin shows every permission the plugin asks for, for the administrator to approve; if a new version asks for more, the plugin stays off until approved again — see [Plugin permissions](/docs/en/store/plugin-permissions)
- The team can suspend a problem plugin (hidden from the store and no longer downloadable), and anyone can press **Report a problem** (&#34;Found a problem?&#34; on the plugin's page of the store website) to report a suspicious plugin

## Badges on plugin cards

| Badge | Meaning |
| --- | --- |
| **Official** | An official plugin from the Anasaki Studio team |
| **Verified developer** | The store's administrators have verified this plugin |
| **Requires system vX+** | Needs this Anasaki Studio version or newer (`minCore`) |
| **Requires** / **Works with** | Other plugins to install first / plugins it works with when present (optional) |

## Categories

`marketing` · `seo` · `forms` · `ecommerce` · `content` · `social` · `analytics` · `design` · `utilities` · `security`

## Next

- Site owners: [Installing, updating and removing plugins](/docs/en/store/install-plugins)
- Developers: [Signing up and publishing plugins](/docs/en/store/publish-plugin)
