We provide security updates for the following versions:
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them via one of the following methods:
- Email: Send details to [your-email@example.com] (or create a security email)
- Subject:
[SECURITY] uAgent Client Vulnerability Report - Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Initial Response: Within 48 hours
- Status Update: Within 7 days
- Fix Timeline: Depends on severity (critical issues get priority)
- Allow us time to fix the issue before public disclosure
- Provide clear, detailed reports
- Act in good faith
- Confirmation of receipt
- Regular updates on fix progress
- Credit for responsible disclosure (if desired)
- Notification when fix is released
When using uAgent Client:
-
Never expose tokens in client-side code
// ❌ DON'T const token = 'bearer-token'; // In frontend // ✅ DO // Keep tokens in server-side only
-
Use environment variables
AGENTVERSE_TOKEN=your-token-here
-
Keep dependencies updated
npm audit npm audit fix
-
Validate all inputs
- Validate agent addresses
- Sanitize user queries
- Check response data
-
Use HTTPS in production
- Always use encrypted connections
- Verify SSL certificates
- Python Bridge Agent: Runs as a local process; ensure proper network isolation
- Token Management: Store tokens securely; never commit to version control
- User Isolation: Use per-user bridges for multi-tenant applications
For non-security bugs:
- Use GitHub Issues
- Follow the bug report template
Thank you for helping keep uAgent Client secure! 🔒