Skip to content

Security: corey924/ZeroSpec

SECURITY.md

Security Policy

Traditional Chinese reference: SECURITY.zh-TW.md

Supported Versions

Version Status
main Supported
Latest tagged release Supported when a fix can be applied cleanly
Older releases Best effort only; you may be asked to upgrade first

Reporting a Vulnerability

Do not open a public issue, pull request, or discussion for a suspected security problem.

Preferred path:

  1. Use GitHub private vulnerability reporting for this repository if it is enabled.
  2. If private vulnerability reporting is not enabled yet, contact the maintainer privately through the contact method published on the maintainer GitHub profile.

Please include:

  • Affected version, tag, or commit.
  • Impact summary.
  • Reproduction steps or proof of concept.
  • Logs, screenshots, or traces if relevant.
  • Any known mitigation or proposed fix.

Response Expectations

  • Initial triage target: within 5 business days.
  • Follow-up timing depends on severity, reproducibility, and maintainer availability.
  • Public disclosure should wait until a fix, mitigation, or coordinated plan is ready.

ZeroSpec is maintained on a best-effort basis. Fast, reproducible reports are the most helpful.

There aren’t any published security advisories