Report vulnerabilities with GitHub's private Security Advisory flow for this repository. If that flow is unavailable, open a public issue containing no vulnerability details and ask the maintainer to establish a private channel. Do not include live credentials, profile archives, private identity material, memory, sessions, or databases in a public issue.
Include the affected version, macOS version, Hermes and Buzz versions, a minimal redacted reproduction, and the security boundary crossed. Replace all secrets with typed placeholders and state whether rotation has already occurred.
Only the latest tagged release receives security fixes. Before the first public tag, the default branch is the supported release-candidate line.
- Credential values are never intentionally printed.
- Shell interpretation is not used for executable or profile inputs.
- Standalone bridge startup fails closed on ambiguous gateway state.
- Credential files must be current-user-owned and inaccessible to group/others.
- The launcher supervises a separate process group and cleans it up on exit.
These guarantees do not protect against a privileged local attacker or a compromised Hermes/Buzz executable.