| Version | Supported |
|---|---|
| 5.x.x | ✅ Actively supported |
| 4.x.x | |
| < 4.0 | ❌ No longer supported |
If you discover a security vulnerability in Alex Cognitive Architecture, please report it responsibly:
Email: Create a private security advisory on GitHub
| Severity | Initial Response | Resolution Target |
|---|---|---|
| Critical | 24 hours | 7 days |
| High | 48 hours | 14 days |
| Medium | 5 days | 30 days |
| Low | 14 days | 60 days |
- Description of the vulnerability
- Steps to reproduce the issue
- Affected versions
- Potential impact
- Suggested fix (if applicable)
- Acknowledgment — We'll confirm receipt of your report
- Investigation — We'll investigate and validate the issue
- Fix Development — We'll develop and test a fix
- Disclosure — We'll coordinate disclosure with you
- Credit — We'll credit you in the release notes (unless you prefer anonymity)
- Local-first design — Data stays on your machine by default
- No telemetry — We don't collect usage data
- Minimal dependencies — Reduced supply chain attack surface
- VS Code sandbox — Extension runs in VS Code's security sandbox
- SecretStorage API — API keys stored encrypted via VS Code
- No hardcoded secrets — All credentials externalized
- Transient tokens — Session tokens not persisted
- HTTPS/WSS only — All external communication encrypted
- Minimal external calls — Only Edge TTS and GitHub (opt-in)
- No data exfiltration — Your code never leaves your machine
- Content Security Policy (CSP) — Prevents XSS attacks
- No inline scripts — All JavaScript in separate files
- Sanitized HTML — User content escaped before rendering
We regularly audit dependencies:
# Check for vulnerabilities
npm audit
# Update dependencies
npm update| Package | Purpose | Risk Level |
|---|---|---|
ws |
WebSocket for TTS | Low (well-maintained) |
fs-extra |
File operations | Low (well-maintained) |
All changes undergo review for:
- Hardcoded secrets
- Unsafe operations (eval, dynamic requires)
- XSS vulnerabilities in webviews
- Path traversal risks
-
npm auditpasses - Dependencies updated
- Security-focused code review completed
- alex_docs/audits/COMPLIANCE-AUDIT.md updated
In case of a security incident:
- Contain — Disable affected functionality
- Investigate — Determine scope and impact
- Fix — Develop and test remediation
- Release — Publish patched version
- Notify — Inform affected users
- Review — Post-mortem and process improvement
Thank you for helping keep Alex safe!