| Version | Supported |
|---|---|
| 4.x | ✅ Yes |
| < 4.0 | ❌ No |
Please do not report security vulnerabilities through public GitHub issues.
Open a private security advisory at: https://github.com/wesleyscholl/vectro/security/advisories/new
Email the maintainer directly. The address is on the GitHub profile.
- A description of the vulnerability and its potential impact
- Step-by-step instructions to reproduce
- Affected versions
- Any known mitigations or workarounds
We follow a 90-day coordinated disclosure policy:
- You report the issue privately.
- We acknowledge receipt within 72 hours.
- We provide a fix or mitigation plan within 14 days.
- After 90 days (or earlier if a fix is shipped), you are free to disclose publicly.
We will credit reporters in release notes unless anonymity is requested.
Vectro is a pure library — no network traffic, no server component, no remote telemetry.
- In scope: memory-corruption bugs in quantization kernels, path-traversal
in file I/O helpers, unsafe deserialization of
.vqzfiles. - Out of scope: vulnerabilities in Hugging Face Hub model downloads
(those are user-initiated and handled by the
huggingface_hublibrary).
If you are unsure whether an issue is in scope, err on the side of reporting privately.