IssueManager releases from main, and only the latest release receives security fixes.
A fix ships as a new release; earlier releases are not patched.
Please do not open a public issue for a security vulnerability.
Report it privately through
GitHub's private vulnerability reporting.
If that isn't available, email matthew.paulosky@outlook.com with the subject [SECURITY] IssueManager.
Please include:
- A description of the vulnerability and its impact
- Steps to reproduce it
- The affected release or commit
- A suggested fix, if you have one
- An acknowledgement within 7 days.
- An assessment, and a plan for a fix if one is needed, once the report is confirmed.
- Credit in the published advisory, unless you prefer to stay anonymous.
Please keep the details private until a fix has been released. Fixed vulnerabilities are published in the repository's security advisories and in the release notes.
- Never commit secrets, API keys or passwords; keep them in untracked local configuration and in repository or environment secrets for CI.
- Keep dependencies current, act on Dependabot security alerts, and check for known vulnerabilities with the ecosystem's audit tool before a release.