Skip to content
SceneCMS
All articles

What shipped in 1.2 — and why the marketplace verifies packages offline

A look at the release that added the marketplace, and the reasoning behind signature checks that need no network.

Version 1.2 added a marketplace to the admin panel: modules and themes installed with one button instead of an FTP client. The interesting part is not the button.

A zip from the internet is code you run

Installing a package means putting PHP files on a server where they execute with the same rights as the product. That is a serious thing to do from a download link, and most plugin ecosystems simply ask you to trust the catalogue.

We did not want that trust to be the only barrier, so a marketplace package is a signed artefact:

marketplace-manifest.json     slug, version, every file with SHA-256
marketplace-manifest.sig      Ed25519 signature of the manifest
files/<path>                  the payload

The public key ships inside the product. Verification happens locally, before extraction, and needs no network — the catalogue can be down, the package is still verifiable.

What is checked, in order

  1. The signature against the installed public key.
  2. The checksum of every file against the manifest.
  3. The slug, type and version inside module.json or theme.json against the signed manifest.
  4. The compatibility range against the CMS version.
  5. That every path stays inside the target directory — path traversal is refused, not sanitised.

A package with one modified byte fails at step 2. A package that claims to be another product fails at step 3.

Installing is not activating

Two decisions that look small and matter in practice:

  • A module is disabled after installation. You enable it when you are ready.
  • A theme is inactive until you press Activate. Nothing changes on the storefront the moment a file lands.

An install that silently alters a live site is impossible to debug on a Friday evening. An install that puts files in place and waits is boring, which is the point.

Rollback is part of install

The previous build moves to storage/app/marketplace/rollback before the new one is swapped in, and the swap is atomic. If the copy fails halfway, the old build is restored and the site keeps rendering.

This is the same principle as the updater: a failed change must leave the system in the state it was in before someone pressed the button.

Licensing without breaking running sites

Installing something new needs a valid license. What is already installed keeps working forever, including after the support year ends.

That asymmetry is deliberate. A lapsed license should pause the shop, not switch off a venue's ticket office on a Saturday. The product blocks the purchase of new things and never touches the site's ability to sell.

Notes from the product