OpenVi Foundation
Docs

Maintained, not archived

We build and maintain open source UI libraries for the web. Components, theming, icons and the tooling around them, all MIT licensed and community run.

Browse projects Read the docs GitHub

What we picked up

Three archived upstream libraries, each with a maintained continuation published under a license that cannot be changed out from under it.

Projects

Three repositories covering the full stack a UI library needs. Each one is versioned and published independently.

  • OpenVue

    continues PrimeVue

    A community-maintained continuation of PrimeVue, one of the most widely adopted Vue.js component libraries, picked up after its original maintainers archived it. 80+ accessible, themeable components for Vue and Nuxt.

    SourceDocsnpm
    v1.0.0
    Vue
    MIT

  • OpenIcons

    continues PrimeIcons

    A community-maintained continuation of PrimeIcons, the icon font used by PrimeVue and the wider Prime ecosystem. 323 icons, shipped as a dependency-free webfont and as tree-shakeable Vue 3 components.

    Sourcenpm
    v1.0.0
    CSS
    MIT

  • OpenUXKit

    continues PrimeUIX

    The styling and theming engine underneath OpenVue, forked from the last MIT-licensed PrimeUIX source and maintained independently. Framework-agnostic.

    Sourcenpm
    v1.1.0
    TypeScript
    MIT

Why the foundation exists

To keep widely used libraries maintained after their original maintainers move on.

  • We started with PrimeVue

    Its last release, 4.5.5, shipped in April 2026 and the repository is archived. The package is still pulled from npm over half a million times a week.

  • The whole stack, in one place

    Components, theming engine and icon set are all maintained here, so nothing critical resolves at runtime from a scope we do not control.

  • MIT, permanently

    Every project here is MIT and stays MIT. A relicense upstream cannot reach these packages.

Migrating from PrimeVue

If you have a PrimeVue v4 project, one command moves it across. It prints a plan first and asks before writing anything. 

npx @openvue/migrate

It renames dependencies, rewrites imports, adds a compatibility override so third-party libraries keep resolving, and leaves a single reviewable diff. Run it with --dry for a preview that writes nothing. The full guide is at openvue.dev/migrate.

Common questions

What people ask most often about PrimeVue being archived and what running OpenVue instead involves.

What is the difference between OpenVue and PrimeVue?
OpenVue continues PrimeVue 4.x with the same component API, so props, slots and events match. The differences are maintenance and ownership: OpenVue is actively released, permanently MIT licensed, and its theming engine and icon set are maintained in the same organization rather than resolved at runtime from a scope the project does not control.
How do I migrate from PrimeVue to OpenVue?
Run npx @openvue/migrate in a PrimeVue v4 project. It prints a plan first, then renames dependencies, rewrites imports and adds a compatibility override so third-party libraries keep resolving, leaving a single reviewable diff. Run it with --dry for a preview that writes nothing.
Is OpenVue free to use commercially?
Yes. Every project the OpenVi Foundation publishes is MIT licensed and stays MIT licensed, which permits commercial use, modification and redistribution. Releases already published cannot be relicensed retroactively.
What replaced PrimeIcons and PrimeUIX?
OpenIcons continues PrimeIcons: 323 icons as a dependency-free webfont or tree-shakeable Vue 3 components, with a compatibility stylesheet so existing pi pi-* class names keep rendering. OpenUXKit continues PrimeUIX, the framework-agnostic theming engine and design tokens that OpenVue renders with.
Does OpenVue work with Nuxt?
Yes. OpenVue ships a Nuxt module, @openvue/nuxt-module, which auto-imports components and needs no configuration. The documentation at openvue.dev covers both Vue and Nuxt setups.
Who maintains OpenVue?
The OpenVi Foundation, an independent group of engineers who know these libraries well. There is no company behind it and no funding. Commit access is granted on sustained, review-quality contribution rather than employer or affiliation.

OpenVi Foundation is not affiliated with, sponsored by, or endorsed by PrimeTek Informatics or PrimeUI.