| Version | Supported |
|---|---|
| 0.1.x | ✅ Yes |
Please do not report security vulnerabilities through public GitHub issues.
If you discover a security vulnerability, please send an email to vibheksoni@engineer.com with:
- A description of the vulnerability
- Steps to reproduce the issue
- Any potential impact
- Suggested fix (if available)
You should receive a response within 48 hours. If the issue is confirmed, we will:
- Work on a fix
- Prepare a security advisory
- Release a patched version
- Credit you for the discovery (if desired)
When using axiomtrade-rs:
- Store credentials in
.envfiles, never in code - Use different credentials for development and production
- Rotate API keys regularly
- Tokens are automatically stored securely by TokenManager
- Set appropriate token expiration times
- Clear tokens on logout
- All API calls use HTTPS/TLS encryption
- WebSocket connections are secure by default
- Rate limiting prevents abuse
- All user inputs are validated before API calls
- Wallet addresses are validated for correct format
- Amount fields check for reasonable ranges
We regularly audit dependencies for known vulnerabilities using:
cargo auditfor Rust dependencies- GitHub Security Advisories
- Dependabot alerts
- Uses industry-standard encryption (P256, PBKDF2)
- Secure random number generation
- Proper key derivation functions
- No custom cryptography implementations
For any security-related questions: vibheksoni@engineer.com