Unless designated otherwise, only the latest release is officially supported. Security fixes will result in a new patch release, at minimum. Significant issues may be backported to prior minor and major versions at the maintainer's discretion.

While minor security issues may be disclosed via a bug report, we do not accept significant security disclosures via public GitHub Issues. We ask that you disclose significant issues privately through GitHub so that we have a chance to mitigate them in the codebase before they become more broadly known.

Examples of security issues which may be disclosed via a bug report include:

• Dependencies with publicly-disclosed issues, e.g., "Dependency (x) needs to be updated."
• Dependencies without active security advisories which have reached end-of-life or which have been abandoned, e.g., "Dependency (x) has reached EOL"

Examples of significant security disclosures which should be disclosed through GitHub's security vulnerability reporting process and not via public bug report include the following:

• Privilege escalation
• Unexpected remote code execution
• Container escape
• Leakage of secure data
• Anything which, given the circumstances, is of equivalent severity to the above

All disclosures must include detailed instructions on reproducing the issue. If possible, please provide a proof of concept or Dockerfile demonstrating the issue so that we can reproduce your environment and respond more quickly.

We will assess the severity of the issue and provide a disposition and timeline directly back to the reporter. The maintainer will coordinate a new release and assess the need for backports.

Once a release has been scheduled, we will work with the reporter on communicating the discovery and resolution of the vulnerability.