OceanApocalypse (OAS) takes security and performance very seriously across all repositories under the OceanApocalypse organization.

If you believe you have found a security vulnerability, please report it to us as shown below.

The following all classify as a security issue:

• Remote code execution: flaws that allow unauthorized code execution on servers or client machines;
• Authentication issues: broken access control allowing privilege escalation, horizontal data leaks (accessing another user's data), or MFA bypasses;
• Injection Vulnerabilities: SQL injections, command injections, LDAP injections, or flawed expression injections.
• Exposure of sensitive data: exposure of secrets and other sensitive data.
• Other security issues.

• Exposure of public data.
• Third-party dependency vulnerabilities: we handle these with tools like Dependabot.
• Anything not related to security: performance issues, security-unrelated bugs, etc.

On GitHub, go to the Security tab (or Security and quality) and click Report vulnerability. Do NOT create a public issue.

Fill in the details and explain the vulnerability as best as possible.

The following table displays the versions of RSML that have on-going support and have constant security updates ( ✅ ) and the ones that don't ( ❌ ).