We release patches for security vulnerabilities for the following versions:
| Version | Supported |
|---|---|
| 1.x.x | ✅ |
We take the security of IP API seriously. If you believe you have found a security vulnerability, please report it to us as described below.
- Email us at security@hmddevs.org with details of the vulnerability
- Provide as much information as possible about the vulnerability
- Allow reasonable time for us to respond before disclosing publicly
- Make a good faith effort to avoid privacy violations, data destruction, or service disruption
- Don't open public GitHub issues for security vulnerabilities
- Don't access or modify data that doesn't belong to you
- Don't perform attacks that could harm the availability of the service
When reporting a vulnerability, please include:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact of the vulnerability
- Suggested fix (if any)
- 24 hours: Initial acknowledgment of your report
- 72 hours: Initial assessment of the vulnerability
- 7 days: Detailed response with planned remediation
- 90 days: Target for vulnerability fix and disclosure
When self-hosting IP API:
- Keep dependencies updated - Regularly run
npm auditand update packages - Use HTTPS - Always serve the API over HTTPS in production
- Rate limiting - Consider implementing rate limiting for high-traffic deployments
- Monitor logs - Keep an eye on access patterns for anomalies
When we receive a security bug report, we will:
- Confirm the problem and determine affected versions
- Audit code to find any similar problems
- Prepare fixes for all supported versions
- Release patches as soon as possible
We appreciate security researchers who help keep IP API safe. Contributors who report valid security issues will be acknowledged in our release notes (unless they prefer to remain anonymous).
Thank you for helping keep IP API and its users safe!
HMD Developments, Inc.