Security updates are actively maintained for the latest stable release of AURA.
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
| < 0.1.0 | ❌ |
The AURA engineering team takes security and reliability seriously. If you discover a security vulnerability, memory safety issue, or potential compromise in AURA, please report it responsibly.
Do not file a public GitHub issue for security vulnerabilities.
Instead, please send a report to the maintainers via:
- Email:
security@grevix.ai - Private Advisory: Use GitHub's Private Vulnerability Reporting feature.
To help us triage and resolve the issue quickly, please include:
- Description of the vulnerability and its potential impact.
- Steps to reproduce the issue (including sample GGUF artifacts, CLI commands, or environment configurations).
- Affected platform(s) (Linux, Windows, macOS).
- Proposed fix or mitigation (if available).
- Acknowledgement: Within 48 hours of report submission.
- Triage & Assessment: Within 5 business days.
- Fix & Disclosure: Critical vulnerabilities will be patched in a security release within 14 days, followed by a coordinated public advisory.
- No Memory Safety Compromises: All crates compile with strict Clippy lints (
-D warnings). - Automated Dependency Audits: Continuous Integration runs
cargo auditto block known advisory vulnerabilities (RUSTSEC). - Strict License & Security Gate:
cargo denyvalidates license cleanliness and banned dependencies on every pull request.