Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Use GitHub's private vulnerability reporting instead: go to the Security tab of this repository and open a draft advisory. This keeps the report private between you and the maintainers until a fix is available.
If you cannot use that, email contact@openvi.dev with SECURITY in the subject line.
Please include as much of the following as you can:
- The affected package and version, and whether it reproduces on the current release.
- The type of issue (XSS, prototype pollution, dependency vulnerability, and so on).
- A minimal reproduction, or the steps and configuration needed to trigger it.
- The impact: what an attacker can do with it.
- We aim to acknowledge a report within 5 working days.
- We will confirm whether we can reproduce it and give you an assessment of severity and a rough timeline.
- We will keep you updated while a fix is prepared, and credit you in the advisory unless you prefer otherwise.
- Once a fix ships, we publish a GitHub Security Advisory and note it in CHANGELOG.md.
OpenVue is maintained by volunteers. We take security reports seriously, but we cannot promise same-day turnaround.
All packages in OpenVue share a single version. Only the most recent release receives fixes.
| Version | Supported |
|---|---|
| Latest 1.x release | Yes |
| Earlier releases | No |
Vulnerabilities inherited from PrimeVue are in scope for OpenVue if they still affect a current OpenVue release. Please report those here as well, because a fix released upstream does not reach OpenVue on its own.
In scope: the packages published from this repository (openvue and @openvue/*).
Out of scope: the openvue.dev documentation site infrastructure, vulnerabilities that require a physically or already fully compromised machine, and reports generated by automated scanners without a demonstrated impact on a consuming application.