We release patches for security vulnerabilities in the following versions:
| Version | Supported |
|---|---|
| 2.x.x | ✅ |
| 1.x.x | ❌ |
The Sapphire team takes security bugs seriously. We appreciate your efforts to responsibly disclose your findings.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them via:
-
GitHub Security Advisories (Preferred)
- Navigate to the repository
- Click on "Security" tab
- Click "Report a vulnerability"
-
Email (Alternative)
- Send details to the maintainers through GitHub profile
- Include "SECURITY" in the subject line
When reporting a vulnerability, please include:
- Type of vulnerability
- Full paths of source file(s) related to the vulnerability
- The location of the affected source code (tag/branch/commit or direct URL)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
- Initial Response: Within 48 hours
- Status Update: Within 7 days
- Fix Timeline: Varies by severity
- Critical: 7-14 days
- High: 14-30 days
- Medium: 30-60 days
- Low: 60-90 days
- Security issues will be disclosed after a fix is released
- We follow coordinated disclosure principles
- We will credit researchers unless they prefer to remain anonymous
When using Sapphire:
- Keep Dependencies Updated: Regularly update to the latest version
- Secure Credentials: Never commit credentials to version control
- Environment Variables: Use environment variables for sensitive data
- Code Review: Review test code for security issues
- Appium Server: Secure your Appium server endpoints
- Cloud Providers: Use secure authentication for cloud device farms
- Appium servers should not be exposed to the public internet
- Test credentials should be stored securely (vault, secrets manager)
- Screenshots/videos may contain sensitive information
- Test data should be sanitized before committing
Thank you for helping keep Sapphire and its users safe!