Private reporting · local-first boundaries

Security

Report vulnerabilities privately and understand the product security baseline before trusting a repository, plugin, agent, or release artifact.

Private channel

Do not open a public issue.

Include affected versions, impact, the smallest safe reproduction, and a suggested mitigation when available. Do not attach secrets or unrelated private repository material.

Open a private advisory

Security baseline

Trust is explicit and bounded.

  • Repositories are untrusted until approved; deterministic discovery never executes commands.
  • Browser access is loopback-only, authenticated, CSRF-protected, and origin-checked.
  • Secrets use operating-system storage and shared redaction before display, persistence, export, or provider use.
  • Agent and plugin capabilities are permission-checked and audited; no generic shell MCP tool exists.
  • Destructive actions require a risk level, preview, and explicit authorization.
  • Release artifacts expose checksums, signing, provenance, and SBOM guidance beside downloads.