Skip to content

Security: openvi-foundation/openux

Security

SECURITY.md

Security policy

Reporting a vulnerability

Please do not report security vulnerabilities through public GitHub issues 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, CSS injection, 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.

What to expect

  • 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.

OpenUXKit is maintained by volunteers. We take security reports seriously, but we cannot promise same-day turnaround.

Supported versions

Each @openuxkit/* package is versioned on its own. Only the most recent release of each package receives fixes.

Version Supported
Latest 1.x release of each package Yes
Earlier releases and 0.x prereleases No

Vulnerabilities inherited from PrimeUIX are in scope for OpenUXKit if they still affect a current release. Please report those here; the @primeuix packages are maintained separately by PrimeTek.

If a vulnerability affects OpenVue through one of these packages, either repository is fine. We will coordinate the fix and the advisories across both.

Scope

In scope: the packages published from this repository (@openuxkit/*).

Out of scope: the read-only upstream clones in submodules/, vulnerabilities that require a physically or already fully compromised machine, and reports generated by automated scanners without a demonstrated impact on a consuming application.

There aren't any published security advisories