Capture All is an early-stage project. Security fixes currently target the latest code on the default branch and the latest published source version. Version 0.1.0 is the current project version; older revisions may not receive fixes.

The project does not currently provide a compatibility guarantee, long-term support schedule, or security response SLA.

GitHub Private Vulnerability Reporting is enabled for this public repository. Submit vulnerability details through the repository's Security tab using Report a vulnerability.

Do not open a public issue for a suspected vulnerability. Do not post real capture data, Bridge tokens, browser content, request or response bodies, credentials, proof-of-concept data from third parties, or unredacted logs in public discussions.

A useful private report includes:

• affected version or commit;
• affected component: extension, Bridge, MCP server, or export;
• reproduction steps using synthetic data;
• expected and observed behavior;
• impact and prerequisites; and
• a minimal proof of concept with all secrets removed.

If GitHub Private Vulnerability Reporting is temporarily unavailable, retain the report privately and share only a non-sensitive notice that the private channel is unavailable. No public security email is currently designated.

The extension requests high-impact browser permissions to capture authorized browser activity. Its Content Security Policy permits scripts only from the extension itself and blocks plugin objects.

Redaction reduces accidental disclosure but is not a complete data-loss-prevention system. Review PRIVACY.md before capturing sensitive sites.

The Bridge is restricted to 127.0.0.1. It rejects other bind addresses, requires a Bearer token on every non-health data endpoint, and restricts browser origins to Chrome extension origins. CORS preflight requests are checked by origin but do not carry application data. Authentication comparison uses a timing-safe hash comparison.

Token model: Two token types are used:

• MCP token: Protects Bridge MCP/CDP routes. Source: explicit CLI/env configuration, or Bridge-generated random token persisted to 0600 file. Stored as SHA-256 hash.
• instance_token: Per-extension enrollment token for extension data routes (/extension/*). Generated by Bridge on enroll, stored as hash, scoped to a single instance. Does not grant access to MCP/CDP routes.

Localhost binding does not protect against every process running on the same machine. Treat all tokens as secrets. Use tokens from explicit configuration or Bridge-generated random values (never hardcoded or example values). Keep .mcp.json local, and stop the Bridge when it is not needed.

Ordinary Bridge JSON bodies are limited to 1 MiB. Extension result bodies are limited to 64 MiB. These are availability limits, not confidentiality controls.

The MCP server communicates over stdio and uses the local Bridge for commands. MCP can return stored capture data to the connected AI agent without a second redaction pass. Only connect agents and services authorized to receive that data.

MCP intentionally does not expose capture deletion or database clearing commands.

Never commit or publish:

• a real Bridge token or local .mcp.json;
• credentials, API keys, cookies, authorization headers, or private URLs;
• unredacted capture exports or browser screenshots containing private data;
• request or response bodies from real users; or
• absolute local paths that reveal private workstation details.

Use clearly invalid synthetic values in tests and reports.

Install dependencies with npm ci from the committed lockfile. Before proposing a security-sensitive change, run:

npm test
npm run build
npm audit --omit=dev
npm audit

A passing dependency audit does not prove the application is free from vulnerabilities.

Allow maintainers reasonable time to reproduce, fix, test, and release a correction before public disclosure. Do not test against systems, accounts, browser profiles, or data without authorization.