Design posture
- Local-first secrets. API keys and tunnel URLs live only in
~/.wednesday/.envon your machine. They are never written to the repository, logs, receipts, task records, or this website. - Workspace confinement. File tools are workspace-confined: a write that escapes the workspace fails, and no tool goes through a shell. Over MCP a run is unattended — the interactive approval preview died with the terminal harness (2026-11-14) — so the workspace boundary, not a prompt, is the trust boundary. Treat the directory you hand a run as one you are willing to have modified.
- Controlled execution. Code changes happen in a sandbox with explicit tools; verification runs real tests plus a security scan, and failures feed a capped repair loop.
- Uninstall is explicit.
wednesday uninstallasks before deleting anything and never touches your projects or checkouts. - Dependency hygiene. Runtime dependencies are pinned; licenses of bundled components are listed in
THIRD_PARTY_LICENSES.md.
Reporting a vulnerability
Please report suspected vulnerabilities privately — do not open a public issue with exploit details:
- Use GitHub's "Report a vulnerability" (Security Advisories) at github.com/lab1207/Wednesday/security/advisories, or
- Contact the maintainer listed in the package metadata (author field of
package.json).
Include: affected version/channel, a description, reproduction steps, and impact. We aim to acknowledge within 72 hours and to publish a fix and a credit (if you want one) for confirmed issues. If a secret of yours may have leaked into a log or receipt, rotate it immediately — wednesday treats keys as compromised once printed.
Scope
In scope: the wednesday CLI and its MCP server, and the packaged runtime. Out of scope: vulnerabilities in third-party model providers, in models you host yourself, or in your own tunnel infrastructure — report those to the respective vendor.