Please do not open a public issue for security vulnerabilities.
Email security@opencoven.ai with:
- A description of the issue
- Steps to reproduce
- Potential impact
We'll respond within 72 hours and coordinate a fix + disclosure timeline with you.
This repo uses gitleaks to prevent accidental secret commits.
For contributors: run script/install-hooks.sh once after cloning. It
installs a pre-commit hook that scans staged changes before every commit.
What's checked:
- Generic high-entropy strings, API keys, tokens (gitleaks default ruleset)
- Apple Developer Team IDs and codesign certificate fingerprints
The release script (script/release.sh) requires two environment variables
that must never be committed:
| Variable | Description |
|---|---|
SIGNING_IDENTITY |
Developer ID Application certificate fingerprint or full identity string |
TEAM_ID |
Apple Developer Team ID |
Store these in your shell profile, macOS Keychain, or CI secrets — never in source files.
If you discover a security vulnerability in OpenCoven, please report it responsibly.
Do not open a public GitHub issue for security vulnerabilities.
Contact the maintainers directly:
- Discord: https://discord.gg/OpenCoven (DM @BunsDev)
- Or open a GitHub Security Advisory on the repository
We will acknowledge receipt within 48 hours and aim to address confirmed vulnerabilities within 14 days.
Security reports are welcome for:
- OpenCoven core harness and routing logic
- OpenTrust memory and session substrate
- Authentication and identity handling
- Agent sandbox and execution boundaries
- Any mechanism that could allow one agent or user to access another's context
- Issues in third-party dependencies (report to the dependency maintainer)
- Issues in model provider APIs (report to the provider)
We take security seriously because OpenCoven handles personal context and agent execution on behalf of users. We will credit researchers who responsibly disclose vulnerabilities (with their permission).
The following properties are design goals of OpenCoven. If you find a way to violate them, that's a security report:
- Session isolation — one user's agent context must not be accessible to another user or agent without explicit permission
- Memory ownership — a user's stored memory and context must remain under their control
- Agent identity integrity — a familiar's identity must not be forgeable by another agent or external caller
- Execution boundaries — agent tool calls must not escape their intended scope
Last updated: 2026-07-04