If you discover a security vulnerability within WrapSplash++, please open a GitHub Issue. All security vulnerabilities will be promptly addressed.

Please do not report security vulnerabilities through public GitHub issues.

When reporting a vulnerability, please include:

1. Description of the vulnerability
2. Steps to reproduce the issue
3. Potential impact
4. Suggested fix (if any)

• Acknowledgment: Within 48 hours
• Initial assessment: Within 1 week
• Fix release: Depends on severity

When using WrapSplash++:

1. Never hardcode credentials in source code
2. Use environment variables or secure vaults for API keys
3. Enable HTTPS for all API communications
4. Validate inputs before processing
5. Keep dependencies updated regularly

This security policy applies to:

• The WrapSplash++ library code
• Build system configurations
• CI/CD pipelines

It does not apply to:

• Third-party dependencies (report to their maintainers)
• Applications using WrapSplash++ (report to their maintainers)

For security-related inquiries, please open a GitHub Issue.