Skip to content
nagi

Marketplace

The Nagi plugin directory lists sandboxed manifest v2 plugins whose published version can be reproduced from an immutable Git commit.

A listing is not a vague trust badge. It exposes the manifest, component checksum, runtime, requested capabilities, automated scan result, publisher, source commit, and capability changes from the previous indexed version.

Install a listed plugin

Section titled “Install a listed plugin”
Terminal window
nagi plugin install owner/repo[/subdir...]
nagi plugin inspect plugin.id
nagi plugin approve plugin.id
nagi plugin enable plugin.id

Marketplace plugins use the WASI component sandbox. A plugin that requests capabilities installs disabled. Approval binds the exact version, manifest, component checksum, commit, and capability set. An update that changes any of those bindings returns to review.

Review labels

Section titled “Review labels”
  • Official: maintained in the Nagi organization and passed the same immutable metadata and automated artifact checks.
  • Verified metadata: source, version, manifest, component checksum, capabilities, and automated scans were reproduced by the registry.
  • Unreviewed: never appears in the install directory. A GitHub topic alone is only a discovery signal.

Verified metadata does not claim that a human audited every line. Stars are popularity metadata, never a security score.

Publish

Section titled “Publish”
  1. Ship a manifest v2 wasi-component plugin with a relative .wasm entrypoint.
  2. Run nagi plugin validate, nagi plugin test, and nagi plugin pack.
  3. Publish the source and component from a public GitHub repository.
  4. Open a registry submission with the repository and intended plugin id.

The registry pins the default branch to a 40-character commit SHA before it fetches the manifest or component. Invalid manifests, native runtimes, oversized artifacts, failed scans, blacklisted repositories, and mutable or missing artifacts fail closed.

Reports and emergency removal

Section titled “Reports and emergency removal”

Report a listing through the Nagi security and abuse intake. Maintainers can disable a repository immediately through the registry kill switch. A failed refresh never overwrites the last known-good snapshot.

For local development and the complete capability model, see Plugins.