We currently provide security support for the following versions:
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
Older versions are not supported and will not receive security fixes.
If you discover a security vulnerability in multiloop, please report it privately so it can be addressed before public disclosure.
How to report:
- Email: hankaihong@outlook.com
- Please include the following information in your report:
- A description of the vulnerability and its potential impact
- Steps to reproduce (or a minimal proof-of-concept)
- Affected version(s) and platform(s)
- Any suggested mitigation, if known
Please do not disclose the vulnerability publicly until it has been addressed.
After we receive your report, we aim to respond as follows:
| Action | Target Timeframe |
|---|---|
| Acknowledgment of the report | Within 48 hours |
| Initial assessment / fix plan | Within 7 days |
| Security fix release (if accepted) | As soon as possible after assessment |
These are best-effort targets, not service-level agreements. Actual response and remediation times may vary depending on the severity and complexity of the issue.
We follow a coordinated responsible disclosure process:
- Report privately via the email above.
- We acknowledge your report within 48 hours and provide an initial assessment within 7 days.
- We work on a fix and release it as a patch to all supported versions.
- Once the fix is released, we disclose the vulnerability details publicly and credit the reporter, unless they prefer to remain anonymous.
We ask that you do not publicly disclose the vulnerability until we have released a fix, to give users time to upgrade.
Security fixes are released as patch releases for all supported versions listed above. Please keep multiloop up to date to receive security fixes.
- Repository: https://github.com/hankaihong1/multiloop
- License: MIT