The following versions receive security updates:
| Version | Supported |
|---|---|
| 0.x | Yes |
If you discover a security vulnerability, please report it responsibly.
Do not open a public GitHub issue.
Instead, use GitHub's private vulnerability reporting to submit your report.
You should receive a response within 72 hours. If the vulnerability is confirmed, we aim to provide a fix within 90 days for non-critical issues, and as quickly as possible for actively exploited vulnerabilities.
We will not pursue legal action against researchers who discover and report vulnerabilities in good faith. We are happy to credit reporters in security advisories unless they prefer to remain anonymous.
This project is designed to handle LLM API keys, sandboxed code execution, and agent-to-tool interactions. As these features are implemented, security-relevant areas include:
- API key and secret management
- Sandboxed code execution boundaries
- Agent permission and approval gates
- Input validation on all external boundaries
- Dependency supply chain (monitored via Renovate and dependency review)
- Ruff bandit rules (S category) check for common security issues in Python code
- CodeQL performs static analysis to find potential vulnerabilities
- Secret scanning and push protection enabled on the repository
- Gitleaks pre-commit hook prevents committing secrets locally + weekly CI workflow
- Renovate monitors dependencies for known vulnerabilities (daily, all ecosystems + CI binary tools via regex managers)
- Dependency review runs on every pull request (license allow-list, PR comment summaries)
- pip-audit scans Python dependencies for known vulnerabilities (every PR + weekly scheduled workflow)
- npm audit scans Node.js dependencies for known vulnerabilities (every PR, critical + high severity)
- Socket.dev GitHub App detects supply chain attacks on PRs (typosquatting, malware, suspicious ownership changes, obfuscated code)
- Trivy scans container images (CRITICAL = hard fail, HIGH = warn-only)
- Cosign keyless image signing for supply-chain integrity (GHCR)
- Hadolint lints all Dockerfiles (backend, web, sandbox) in CI + pre-commit hook
- Chainguard Python distroless runtime (non-root, CIS Docker Benchmark v1.6.0 hardened)
- Zizmor static analysis of GitHub Actions workflows (SARIF uploaded on push events only; fork PRs lack
security-events: write) - OSSF Scorecard supply chain maturity scoring (SARIF to Security tab, weekly + push to main)
- All workflow actions pinned by full SHA with version comments
permissions: {}at workflow level with least-privilege per jobpersist-credentials: falseon allactions/checkoutsteps- Signed commits required on
mainvia branch protection
- ZAP API Scan runs against the backend OpenAPI spec (push to main + weekly)
- Results available as workflow artifacts (SARIF upload planned when ZAP action adds native support)