Trusted marketplace
Trusted marketplace
The Marketplace page in Settings > Plugins & Skills shows three separate trust tiers, cached
catalog packages, and installed/staged versions. Before activation it shows the exact publisher,
version, compatibility, permissions, data access, tests, review status, signature key, digest,
maintenance status, and advisories. You must check the exact-version review box before activation.
Important trust distinctions
- Signed means the package matches bytes signed by a configured publisher key.
- Identity verified means the registry/operator separately verified that publisher.
- Reviewed means recorded automated or human review completed for this version.
- Contained describes the runtime boundary for executable extensions.
- Popular is not evidence that a package is safe.
These facts reinforce each other but are not interchangeable.
Rollout
Remote catalog refresh/download is disabled by default:
HOLARYN_MARKETPLACE_ENABLED=false
Set it to true and restart only after the configured registry and publisher trust roots have been
reviewed. Status, signed package verification, authoring, and policy-approved offline import remain
available while remote rollout is disabled.
Inspect and search
uv run holaryn marketplace status
uv run holaryn marketplace refresh io.example.registry https://registry.example/index.json
uv run holaryn marketplace search "calendar maintained" --compatible
uv run holaryn marketplace search --quality maintained --compatible
uv run holaryn marketplace search --tier content_only
uv run holaryn marketplace inspect io.example.calendar --version 1.2.0
Search requires every query token to match. Identity matches rank above categories/quality, which
rank above description. The CLI prints the ranking reason.
Install and activate
Catalog installation downloads and verifies an immutable version, then stages it without
activation:
uv run holaryn marketplace install io.example.calendar --version 1.2.0
uv run holaryn marketplace inspect io.example.calendar --version 1.2.0
uv run holaryn marketplace activate io.example.calendar 1.2.0
Activation prints the exact trust/permission review and asks for confirmation. --yes records that
the operator reviewed the displayed version; it is appropriate only in a separately reviewed
automation workflow. A package that expands permissions requires fresh consent.
The host refuses an incompatible, revoked, tampered, dependency-incomplete, conflicting,
policy-denied, or ordinary downgrade activation.
Marketplace activation selects the verified package version; it does not collapse the package's
inner runtime boundary. A content-only skill becomes discoverable but its scripts remain untrusted.
Plugins/connectors and executable extensions remain disabled at their existing execution controls
until those processes, destinations, permissions, and runtime rollout are separately enabled.
Update, pin, rollback, and disable
uv run holaryn marketplace update io.example.calendar --version 1.3.0
uv run holaryn marketplace activate io.example.calendar 1.3.0
uv run holaryn marketplace pin io.example.calendar 1.3.0
uv run holaryn marketplace unpin io.example.calendar
uv run holaryn marketplace rollback io.example.calendar
uv run holaryn marketplace disable io.example.calendar
uv run holaryn marketplace remove io.example.calendar --yes
Installing an update leaves the current version active until explicit activation succeeds. A pin
prevents another version from becoming active. Rollback is the only supported downgrade path and
restores the previous immutable version; executable extensions also restore its configuration
snapshot. Disable prevents use in new sessions while retaining recovery evidence. Remove deletes
all marketplace-managed versions after dematerializing the active package.
Offline and air-gapped use
uv run holaryn marketplace verify X:\approved\package.holaryn-marketplace
uv run holaryn marketplace import X:\approved\package.holaryn-marketplace
Verification is read-only. Import requires policy approval for offline media, publisher, package,
and signing key. A private registry or mirror uses the same signed index/package formats and must
match the exact locked policy location.
Advisories and recovery
Registry refresh verifies the signed advisory feed. If an active version is revoked, Holaryn rolls
back to a non-revoked previous version when one exists; otherwise it disables the package. The
Marketplace page and CLI status show diagnostics for expired indexes, corrupt archives, unknown
trust roots, and policy refusal.
If recovery is needed:
- do not edit an installed package or the marketplace state file;
- disable the package;
- refresh the trusted registry or obtain a verified offline archive;
- inspect the advisory and exact immutable version;
- unpin only when the replacement/rollback has been reviewed; and
- activate or roll back through the CLI or Settings page.
Queue a registry report with holaryn marketplace report; review the local report before sending it,
and never include secrets or user content.