Supported version
Security fixes target the latest commit on main. There is not yet a multi-version support matrix.
Report a vulnerability privately
Use GitHub Private vulnerability reporting when it is available for this repository. Include the affected commit, impact, a minimal reproduction using example data, and any suggested mitigation.
Exclude browsing content, credentials, databases, API keys, and public exploit details. If private reporting is unavailable, open a public issue without exploit details and ask the maintainer to establish a private channel.
Local security boundaries
- The local HTTP service refuses non-loopback binds and validates request host, browser origin, and extension origin.
- The release extension package and local service share one verified extension identity; other extension origins are rejected.
- Protection checks fail closed before page text is read, again at local-service ingestion, and again before agent access.
- MCP tools are non-destructive; destructive controls are not exposed to agents. Calls retain bounded local query metadata for owner-visible activity, not returned evidence snippets.
- An agent with separate shell or filesystem access is outside the MCP-only boundary.
- Setup writes require explicit flags, back up existing files, preserve unrelated settings, and refuse unsafe conflicts.
- Memory and service logs use owner-only permissions in the managed macOS data directory.
- Provider prompts treat saved page content as untrusted quoted data.
Not security bugs by themselves
- A person with access to your local macOS account can access your local files.
- Enabled Chrome profiles under one macOS user share one Daemon service and vault.
- An owner can deliberately export or inspect their own database.
- Uninstalling the service preserves the database by design.
- Contributors can load the unpacked extension in Developer mode.
- Unverified Chromium browsers are not security-compatibility claims.
Safe testing
Use the included isolated smoke and MCP proof scripts. They create temporary databases and must never be pointed at real private memory. Do not test destructive behavior against another person's machine or data.
python3 tools/package-extension-proof.pyRelease ZIPs must come from the deterministic packaging workflow and be checked against the intended file inventory and SHA-256 checksum.