NEXUS accepts external input through GitHub Issues, which is an inherent attack surface. The system is designed with defense-in-depth to prevent prompt injection, cost abuse, and memory manipulation.
- Prompt injection detection — 20+ regex patterns scan all issue titles and bodies before they reach the AI
- Cost abuse limits — hard caps on issues per session (5), total chars (4,000), output tokens (4,096), rules per session (2)
- Memory integrity — AXIOM's output is sanitized before writing to
memory/. Rule weights clamped to 1-10, categories validated against allowlists - Foundational rule protection — rules r001-r010 cannot be deleted, minimum 5 rules enforced
- System prompt cap — 8,000 character limit prevents unbounded growth
| Version | Supported |
|---|---|
| latest (main) | Yes |
If you discover a security vulnerability — especially a way to bypass the prompt injection filter or manipulate NEXUS's memory through crafted input — please report it responsibly.
Do NOT open a public issue for security vulnerabilities.
Instead, please use one of the following:
- GitHub Security Advisories — go to the Security tab and create a private advisory
- Direct contact — reach out to the maintainer directly through GitHub
- Bypassing the prompt injection filter in
security.ts - Manipulating NEXUS's rules or system prompt through crafted issue content
- Causing NEXUS to exceed cost limits (token, issue, or rule caps)
- Getting NEXUS to leak its API key or system prompt
- XSS or injection through the GitHub Pages journal site
- Any way to make NEXUS delete its foundational rules
- NEXUS making a bad market analysis — that's a feature request, not a security issue
- NEXUS ignoring your suggestion — that's by design
- Disagreeing with NEXUS's confidence score — open a feedback issue instead
Security reports will be acknowledged within 48 hours. Confirmed vulnerabilities will be patched and credited (unless you prefer anonymity).