Marketplace security
What an extension can run, which permissions it asks for, how releases are signed and checked, and what uninstalling puts back. Each point below is a rule the platform enforces in its own code, not a promise made by a developer.
What an extension can run
- Themes, document designs, industry websites and the data packs (website content, automation recipes, print templates, page designs, demo data, e-mail texts, assistant questions, tax and language packs) are data. Nothing in them is executed; an install writes only the values the automated checks accepted.
- Themes contain no server code: a theme sets colours, corner radius, fonts from the bundled list and the header and footer layout.
- Website widgets are a template and styles. A widget's optional script runs only inside a sealed frame on your website, without network access, cookies or access to the page around it.
- Integrations run on the developer's own servers. They reach your workspace only through an API key limited to the scopes you approve and the events you approve; wildcard scopes and events are refused.
- Plugins come in two forms: declarative plugins (one file, no code: the platform carries out a closed list of effects, each behind a permission) and code plugins, which are switched on only once the plugin ships as part of a zmle platform release.
Plugins: no network, no environment, no other plugin's data
Every file of a code plugin passes an automated scan. A package is refused when it uses any of the following:
- Network access: fetch, XMLHttpRequest, WebSocket, EventSource and sendBeacon. Anything that talks to another service has to be an integration.
- Environment variables, the process object, the file system, child processes and Node internals.
- Direct database access. A plugin keeps its data in its own store, and every store call must name the plugin's own id, so it can never read another plugin's data.
- eval, Function, dynamic import or require. Only a short list of imports is allowed.
- Cookies, browser storage, postMessage and raw HTML injection; minified or obfuscated code.
- Public API routes or a database schema of its own. Plugin pages live inside the admin area only.
- A package that declares network hosts or environment variables is refused outright.
Permissions you see before installing
- A plugin lists its capabilities: its own store, settings, event hooks, filters, dashboard cards, scheduled jobs, admin pages, messages and actions. The check refuses a package whose code or manifest uses a capability it did not declare.
- Plugins and integrations must describe in the package which workspace data they read or store, and why.
- A declarative plugin asks for each effect by name, for example creating tasks, notifying staff or receiving one business event with its documented fields only. The permission is checked again every time the plugin runs.
- Each listing page shows what the release can access, taken from the automated check of the signed version.
Signing and verification
- When a release is approved, the platform signs it with an Ed25519 key. The signature covers the listing, the version, the size and the SHA-256 hash of the package.
- Before every install and update, the stored package is hashed again and the signature is checked against the platform's trusted keys. If either check fails, nothing is installed.
- The install uses the normalised package the automated checks produced, never the developer's raw upload.
- A declarative plugin can also carry its developer's own signature. Once a release is signed, every later release must be signed with the same developer key.
- When the platform key is rotated, the earlier public keys stay trusted, so releases signed before keep verifying.
Suspension
- A suspended or delisted listing can no longer be installed or updated.
- Suspending a seller suspends all of that seller's published listings.
- Subscriptions to a suspended or delisted listing are not renewed; a free trial that ends in that state expires and the extension is switched off in the workspace.
What uninstalling puts back
- Theme: your previous colours, fonts and layout come back.
- Integration: its API key is revoked, its webhook endpoint is deleted and the developer's server is told.
- Document design: the added design is removed, unless you made it your default.
- Website widget: the block is removed from the page builder.
- Plugin: it is switched off in your workspace; its own stored data stays until you delete it.
- Company stamp, label stock, document language, e-mail wording, task rules and automations: the previous values come back.
- Reply texts, assistant questions and demo data are removed; a page design is removed while it is still a draft; country settings are undone and unused tax rates are removed.
- Industry websites, content packs and ledger accounts: what they added stays, because it is your content (or may carry your entries) now. The website from before an industry install is kept as a backup.
Related
To report a listing, use the Report link on its page.
Privacy policyData processing agreementSub-processorsMarketplaceSell on the marketplace