Skip to content

The agent that grows with you

docs(plugin-catalog): password-manager plugins are listed only from their vendor

Teknium69fb5c10eddf
diff --git a/plugin-catalog/README.md b/plugin-catalog/README.md
index 92bdae26ea3..437b8563eb2 100644
--- a/plugin-catalog/README.md
+++ b/plugin-catalog/README.md
@@ -154,6 +154,17 @@ meaningful:
<pinned sha>`). A binary a user's own machine fetches at setup time is allowed
only from the upstream tool's official source, pinned by checksum, and
disclosed (rule 13) — never bundled and never from an unofficial mirror.
+18. **Password managers come from their vendor.** A plugin that registers a
+ `browser_vault` login backend (`ctx.register_login_backend`) is listed only at
+ `tier: verified`, submitted from the password-manager vendor's own repository
+ by that vendor, or at `tier: official` when Nous maintains it. Community-tier,
+ fork and third-party listings of a login backend are declined. Hermes enforces
+ the same rule when the plugin loads: a login backend is accepted only from a
+ plugin bundled with Hermes or installed from this catalog at `verified` or
+ `official` tier and at the reviewed pin, as recorded in Hermes's own install
+ record (never a file inside the plugin). Local-directory, Git URL, `--ref`,
+ `--allow-removed`, project and pip installs are refused, and no setting
+ relaxes it.
<!-- admission-rules:end -->
The step-by-step submission guide, with the same rules and what reviewers check,
diff --git a/website/docs/developer-guide/browser-vault-plugin.md b/website/docs/developer-guide/browser-vault-plugin.md
index be40dd3068e..c90e9dfbfed 100644
--- a/website/docs/developer-guide/browser-vault-plugin.md
+++ b/website/docs/developer-guide/browser-vault-plugin.md
@@ -6,7 +6,8 @@ description: Add a password manager to browser_vault with ctx.register_login_bac
# Browser Vault Plugins
A plugin can add a password manager (KeePass, a team vault, a hardware-backed store) as a login
-source for the `browser_vault` tool. The agent then lists and fills that manager's logins the same way
+source for the `browser_vault` tool, when it comes from a verified source: the manager's vendor
+through the plugin catalog, or Nous (see [Who can register a backend](#who-can-register-a-backend)). The agent then lists and fills that manager's logins the same way
it does for the built-in Hermes vault, 1Password and Bitwarden: it sees handles and metadata, never a password.
Browser login backends are separate from [secret sources](./secret-source-plugin.md). A `SecretSource`
@@ -51,6 +52,27 @@ vault:
Construct the backend without fetching credentials or reading profile state, and read the active
profile's configuration lazily. Registration is profile-scoped and removed when the plugin unloads.
+## Who can register a backend
+
+Password-manager integrations come only from verified sources. `ctx.register_login_backend` is
+accepted from:
+
+- a plugin bundled with Hermes, or
+- a plugin installed from the [Hermes plugin catalog](./plugins/catalog-submission.md) at
+ `tier: verified` (published by the password-manager vendor itself) or `tier: official`
+ (maintained by Nous), at the catalog's reviewed pin.
+
+Every other plugin is refused at registration with a log line naming this rule: a plugin dropped
+into `~/.hermes/plugins/` by hand, a Git URL install, a community-tier catalog entry, a catalog
+install moved off its pin with `--ref`, one installed with `--allow-removed`, a project plugin and
+a pip entry-point plugin. Provenance is read from Hermes's own install record
+(`plugins/.install-metadata.json`, written by the installer), never from a file inside the plugin, so
+a repository that ships its own `.hermes-catalog.json` gains nothing. No config key relaxes the rule.
+
+If you build a password manager and want it in Hermes, submit the plugin to the catalog from your
+own repository and ask for `verified` tier (catalog admission rule 18). Integrations for managers
+whose vendor has not published one come from Nous as `official` entries.
+
## Isolation rules
Hermes wraps every plugin backend in a core-owned adapter before the vault tool sees it. These rules
@@ -69,7 +91,8 @@ hold however the plugin implements its class:
An in-process plugin is ordinary Python running inside Hermes, so these rules are an API contract,
not a sandbox. They guarantee that Hermes never hands your backend another backend's data; they do not
-stop arbitrary code in the same process from reading files. Install password-manager plugins you trust.
+stop arbitrary code in the same process from reading files. The provenance rule above decides which
+plugins Hermes offers this seam to; it is not a sandbox either.
## Fill context
diff --git a/website/docs/developer-guide/plugins/catalog-submission.md b/website/docs/developer-guide/plugins/catalog-submission.md
index 06a3d197f36..6561a2a0c82 100644
--- a/website/docs/developer-guide/plugins/catalog-submission.md
+++ b/website/docs/developer-guide/plugins/catalog-submission.md
@@ -212,6 +212,17 @@ the gallery. There is no separate listing to maintain.
<pinned sha>`). A binary a user's own machine fetches at setup time is allowed
only from the upstream tool's official source, pinned by checksum, and
disclosed (rule 13) — never bundled and never from an unofficial mirror.
+18. **Password managers come from their vendor.** A plugin that registers a
+ `browser_vault` login backend (`ctx.register_login_backend`) is listed only at
+ `tier: verified`, submitted from the password-manager vendor's own repository
+ by that vendor, or at `tier: official` when Nous maintains it. Community-tier,
+ fork and third-party listings of a login backend are declined. Hermes enforces
+ the same rule when the plugin loads: a login backend is accepted only from a
+ plugin bundled with Hermes or installed from this catalog at `verified` or
+ `official` tier and at the reviewed pin, as recorded in Hermes's own install
+ record (never a file inside the plugin). Local-directory, Git URL, `--ref`,
+ `--allow-removed`, project and pip installs are refused, and no setting
+ relaxes it.
<!-- admission-rules:end -->
## Updating your entry