| Version | Supported |
|---|---|
| main (pre-release) | ✅ Active development |
| < 1.0.0 |
Do NOT open a public GitHub issue for security vulnerabilities.
Report security issues privately:
- Email: jbrashear@titaniumcomputing.com
- Subject line:
[SECURITY] ArgentMunch - <brief description> - Expected response: Within 72 hours
- Resolution target: Critical issues patched within 7 days
Include in your report:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (optional)
ArgentMunch indexes source code. The following rules apply to all indexed data:
- Local-only by default — indexed symbol data stays on the machine running the server
- No telemetry — ArgentMunch does not phone home or transmit code to external services
- Index storage — stored in
~/.code-index/(local disk only) - No cloud sync — index data is never synced to external storage without explicit operator configuration
- Sensitive file detection — files matching secret patterns are excluded from indexing (see below)
ArgentMunch only indexes repos that are explicitly configured by the operator.
- No auto-discovery of repos on disk
- Repos must be explicitly added to the index configuration
- Wildcards require explicit opt-in
- MAO agents may only query repos in the allowlist — no arbitrary repo access
ArgentMunch never indexes files matching these patterns:
.env
.env.*
*.key
*.pem
*.p12
*.pfx
*.cert
*.crt
secrets/
.secrets/
credentials/
config/secrets*
**/*secret*
**/*password*
**/*token*
**/*api_key*
These exclusions are enforced at the file discovery layer — matching files are skipped before any content is read.
Additional hardening:
- Symbol extraction never logs file content — only symbol names, types, and locations
- Query results never return raw file content — only structured symbol metadata
ArgentMunch inherits the following security controls from jCodeMunch:
- Path traversal prevention — all paths validated to be descendants of repo root
- Symlink escape protection — symlinks outside repo root are rejected
- GitHub API token scoping — only
repo:readscope required
See upstream SECURITY.md for full upstream controls.
Last updated: 2026-03-04 | ArgentOS / ArgentAIOS team