Skip to content

Latest commit

 

History

History
35 lines (24 loc) · 2.13 KB

SECURITY.md

File metadata and controls

35 lines (24 loc) · 2.13 KB
Raw

Security Policy

Supported Versions

Version Supported
2.x ✅
1.x ❌

Legend:

  • ✅ Currently supported, receives all security and other updates
  • 🔙 Legacy support, receives backported security updates only
  • ❌ Unsupported

Reporting a Vulnerability

Please report known and suspected vulnerabilities privately and responsibly disclosed by filling out a vulnerability report on Github1. Vulnerabilities may also be privately and responsibly disclosed by emailing all pertinent information to security@timozacherl.com.

⚠️ Please do not file a public issue! ⚠️

When to report a vulnerability

  • You think you have discovered a potential security vulnerability in SwiftLogLoki.
  • You are unsure how a vulnerability affects SwiftLogLoki.

What happens next?

  • I will acknowledge receipt of the report within 3 working days. This may include a request for additional information about reproducing the vulnerability.
  • Once I have identified a fix I may ask you to validate it. I aim to do this within 30 days. In some cases this may not be possible, for example when the vulnerability exists at the protocol level and the industry must coordinate on the disclosure process.
  • If a CVE number is required, one will be requested through the GitHub security advisory process, providing you with full credit for the discovery.
  • I will decide on a planned release date and let you know when it is.
  • Prior to release, I will inform major dependents that a security-related patch is impending.
  • Once the fix has been released I will publish a security advisory on GitHub.

Footnotes

  1. See Github's official documentation of the vulnerability report feature for additional privacy and safety details. ↩