Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

osc plugin install

Install a wasm auth plugin, from the registry by name or from a local .wasm file.

osc plugin install <name> resolves <name> against the registry index (latest version, or <name>@<version> to pin a specific one), downloads it, verifies its checksum and — unless --allow-unsigned is given — its GitHub artifact attestation, shows what was found, and asks for confirmation (skippable with --yes).

osc plugin install --file <path> installs a local .wasm file instead. A local file has no provenance to verify, so this always requires --allow-unsigned. In both cases the plugin is loaded and its ABI is validated before anything is written to the plugin directory, and installing over an already-installed name@version fails unless --force is given.

Usage: osc plugin install [OPTIONS] [SPEC]

Arguments:

  • <SPEC> — Plugin to install: <name> (latest) or <name>@<version> (pinned), resolved against the registry index. Omit when using --file

Options:

  • --file <FILE> — Install from a local .wasm file instead of the registry. Local files have no provenance to verify, so this always requires --allow-unsigned
  • --version <VERSION> — Version to record a --file install under. Defaults to 0.0.0 when not given. Ignored for registry installs — use <name>@<version> in the positional argument instead
  • --force — Replace an existing installation of the same name@version
  • --registry-url <REGISTRY_URL> — Registry index URL to resolve against. The pinned default is never silently overridden by anything but this explicit flag
  • -y, --yes — Proceed without an interactive confirmation prompt
  • --allow-unsigned — Install even though the plugin’s provenance could not be verified (required for --file, since a local file has no provenance to check). Loudly logged