| Version | Supported |
|---|---|
| 1.1.x | ✅ |
- The library enforces TLS 1.2 or higher by default
- Certificate validation is enabled by default
- Custom certificate validation can be configured via RequestConfig
- Supports API Key and OAuth token authentication
- Keys should be stored securely (not hardcoded)
- Use environment variables or secure configuration management
- Always use HTTPS for production environments
- Keep the library updated to the latest version
- Enable SSL certificate validation
- Set appropriate timeouts
- Use rate limiting to prevent abuse
- Implement proper error handling
- Validate all input URLs and data
Network::RequestConfig config;
config.verify_ssl = true;
config.use_tls12_or_higher = true;
config.timeout_seconds = 30;
config.api_key = getSecureApiKey(); // Get from secure storageIf you discover a security vulnerability, please follow these steps:
- Open a public issue
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)