| Version | Supported |
|---|---|
| 2.1.x | Yes |
| < 2.1 | No |
If you discover a security vulnerability in AIPass, please report it responsibly.
Do not open a public GitHub issue for security vulnerabilities.
Instead, use one of these methods:
- GitHub Security Advisories (preferred): Report a vulnerability
- Email: aipass.system@gmail.com
- Description of the vulnerability
- Steps to reproduce
- Affected version(s)
- Any potential impact
- Acknowledgment within 48 hours
- Status update within 7 days
- Fix timeline communicated once the issue is confirmed
- AIPass Python package (
src/aipass/) - CLI entry points (
drone,aipass) - Hook handlers (
src/aipass/hooks/apps/handlers/) - GitHub Actions workflows (
.github/workflows/)
- Third-party dependencies (report upstream)
- Issues requiring physical access to the machine
- Social engineering
AIPass runs locally. No data leaves your machine unless you explicitly configure external services.
- Secrets are stored outside the repo at
~/.secrets/aipass/and never committed - API keys are handled by the
apibranch and never logged or exposed in output - Git operations are sandboxed through
drone @gitwith permission deny lists - Hook handlers are native Python handlers routed through the hook engine