Soplang Security Policy
We take the security of Soplang seriously. This policy outlines how to report vulnerabilities and our commitment to addressing security issues.
Reporting a Vulnerability
Do not report security vulnerabilities through public GitHub issues or community forums.
Please report security vulnerabilities by emailing our security team at: security@soplang.org
Please include the following information in your report:
- Type of vulnerability
- Path or location of the vulnerable code
- Step-by-step instructions to reproduce the issue
- Explanation of potential impacts
- Suggested fix, if available
Our security team will acknowledge your email within 48 hours, and you'll receive a more detailed response within 72 hours indicating the next steps in handling your report.
Disclosure Policy
When we receive a security vulnerability report, we will:
- Confirm the vulnerability and determine its scope
- Develop and test a fix
- Prepare an update that addresses the vulnerability
- Release the update and credit the reporter (unless they prefer to remain anonymous)
We ask that you give us reasonable time to address the vulnerability before any public disclosure. We typically address critical issues within 7-14 days.
Security Best Practices
To keep your Soplang projects secure:
- Keep Soplang and its dependencies updated to the latest versions
- Follow secure coding practices, especially when handling user input
- Regularly review and update your dependencies
- Be cautious when running untrusted Soplang code
- Use dependency scanning tools to identify vulnerabilities
Bug Bounty Program
While we currently do not have a formal bug bounty program, we deeply appreciate the efforts of security researchers and the community in identifying and reporting vulnerabilities.
We acknowledge all reporters in our security releases unless they wish to remain anonymous.
Additional Resources
Secure Coding Guidelines
Learn about secure coding practices specific to Soplang.
View Secure Coding Guide