Skip to content

Marketplace

Marketplace is where you discover packs and plugins. It should make publisher identity, capability scope, and review state visible before installation.

ItemPurpose
PluginConnects Stallari to a service or local capability.
PackAdds workflows, prompts, and configuration around a use case.
Sealed packProvides restricted or commercial content where supported.

Marketplace entries should show enough information to support a deliberate install decision:

  • publisher,
  • version,
  • compatibility,
  • certification or review state,
  • required service contracts,
  • data classes,
  • action classes,
  • network behavior,
  • and pricing or license state where relevant.

Community content can be useful, but it should not look equivalent to first-party reviewed content.

A typical install flow previews the entry, checks compatibility, binds required services, downloads the manifest or artifact, and then records the installed state.

Sensitive plugins still need consent before first use or capability expansion. Installing a plugin is not the same as allowing it to read private data or perform actions.

Marketplace may show cached data if the registry is unavailable. Cached data is useful for browsing installed or recently seen entries, but refresh before making trust decisions.

SymptomWhere To Check
Registry unavailableNetwork state, then retry refresh.
Install blockedCompatibility, license, missing plugin contracts, or permission requirements.
Plugin installed but unusableSettings for credentials and Status for readiness.
  • Packs And Trust — the trust chain, integrity hashes, and capability scoping behind every install
  • Agency Model — installing a pack extends agency through scoped, gated capabilities