We take the security of Pen2PDF seriously. If you discover a security vulnerability, please help us protect our users by reporting it responsibly.
Please DO NOT report security vulnerabilities through public GitHub issues.
Instead, please report security vulnerabilities by:
-
GitHub Security Advisories (Preferred):
- Go to the Security tab of our repository
- Click "Report a vulnerability"
- Fill out the security advisory form
-
Email Contact:
- Send an email to the maintainer via GitHub profile
- Include "SECURITY" in the subject line
- Provide detailed information about the vulnerability
When reporting a security vulnerability, please include:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact of the vulnerability
- Suggested fix (if you have one)
- Your contact information for follow-up questions
- Initial Response: Within 48 hours of your report
- Status Update: Within 7 days with an assessment of the report
- Resolution: We aim to resolve critical vulnerabilities within 30 days
We provide security updates for the following versions:
| Version | Supported |
|---|---|
| Latest | β Yes |
| < 1.0 | β No |
When contributing to or using Pen2PDF:
- Keep your API keys secure and never commit them to version control
- Use environment variables for sensitive configuration
- Regularly update to the latest version
- Report suspicious behavior or potential vulnerabilities
- Follow secure coding practices
- Validate all user inputs
- Use HTTPS for all communications
- Keep dependencies updated
- Never commit secrets or sensitive data
Pen2PDF implements several security measures:
- Environment Variable Protection: API keys stored in environment variables
- Input Validation: Server-side validation of file uploads and user inputs
- CORS Configuration: Proper CORS setup for API endpoints
- File Type Validation: Strict file type checking for uploads
- Rate Limiting: Protection against abuse (when implemented)
The following are generally considered out of scope for security reports:
- Issues in third-party dependencies (report to the respective maintainers)
- Social engineering attacks
- Physical attacks
- Denial of service attacks requiring excessive resources
We believe in recognizing security researchers who help keep our project safe:
- Security researchers will be credited in our security advisories (with permission)
- We maintain a security acknowledgments section for significant contributions
- We may feature notable security contributions in our release notes
If you have questions about this security policy, please open a regular GitHub issue with the question label or contact the maintainers through GitHub.
Remember: When in doubt, please report it. We'd rather investigate a false positive than miss a real security issue.
Thank you for helping keep Pen2PDF and our users safe! π