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.
What we forked
The full stack a UI library needs
-
OpenVue
Stable, versionv1.1.0forked from PrimeVue
Accessible Vue UI components, MIT licensed and community maintained.
npm install openvue @openvue/themesVue · MIT -
OpenIcons
Stable, versionv1.1.0forked from PrimeIcons
An MIT-licensed icon set for OpenVue and the web.
npm install @openvue/openiconsCSS · MIT -
OpenUXKit
Stable, versionv1.2.0forked from PrimeUIX
The framework-agnostic UI foundation behind OpenVue.
npm install @openuxkit/themesTypeScript · MIT -
OpenVolt
Stable, versionv1.1.0forked from PrimeVue Volt
Tailwind CSS components for OpenVue that you copy and own.
npx openvolt-vue add ButtonVue · MIT
Why the foundation exists
-
We started with PrimeVue
The MIT 4.x line last shipped in April 2026 and now gets security fixes only, while new development moved off MIT. It is still pulled from npm over 400,000 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.
Common questions
Something else? Ask on Discord or write to contact@openvi.dev.
- What is the OpenVi Foundation?
- An independent, community-run organization that maintains open source UI libraries for the web. It forks widely used MIT-licensed front-end libraries when their MIT line stops being developed, and keeps those forks released, documented and MIT licensed.
- Which projects does the foundation maintain?
- Four libraries, each an MIT-licensed fork: OpenVue, the Vue component library forked from PrimeVue 4.5.5; OpenVolt, Tailwind CSS components forked from Volt; OpenIcons, forked from PrimeIcons; and OpenUXKit, the theming engine forked from PrimeUIX. It also publishes templates and starters such as the Deni admin dashboard.
- Are the projects 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.
- Who runs the foundation, and who funds it?
- A group of engineers who know these libraries well, together with a growing set of community contributors. There is no company behind it and no funding. Commit access is granted on sustained, review-quality contribution rather than employer or affiliation.
- How can I contribute?
- Pick an issue on any of the project repositories, report a bug with a reproduction, improve the documentation, or test components with assistive technology. Each project lists where help is needed most on the contribute page, and conversation happens on Discord.
- I use PrimeVue. Where do I start?
- With OpenVue, which keeps the PrimeVue 4 component API. Running
npx @openvue/migratein a PrimeVue 4 project renames the packages and rewrites the imports in one reviewable diff, and the OpenVue migration guide covers icons, Volt and older versions. - Is the foundation affiliated with PrimeTek?
- No. The OpenVi Foundation is not affiliated with, sponsored by, or endorsed by PrimeTek Informatics or PrimeUI. The projects are forks made under the MIT license the original code was released with, and they keep PrimeTek's copyright notice. PrimeVue, PrimeIcons, PrimeUIX, Volt and PrimeTek are names of their respective owners, used here only to describe where the code came from.
Help keep it maintained
Triage an issue, test a release against your app, or fix a doc. Commit access follows sustained contribution, not affiliation.
OpenVi Foundation is not affiliated with, sponsored by, or endorsed by PrimeTek Informatics. PrimeVue, PrimeIcons, PrimeUIX and Volt are names of their respective owners, used here only to describe where our forks came from.