About the foundation
An independent organization that builds and maintains open source UI libraries for the web.
What we do
We maintain the parts of the front-end stack that applications sit on top of: component libraries, theming engines, icon sets and the tooling around them. Everything we publish is MIT licensed and developed in public.
Maintenance is the actual product. Plenty of open source gets written; much less of it gets kept working across framework releases, browser changes and security advisories for years afterwards. That long tail is the work we take on.
How we got here
The foundation formed around PrimeVue after its original maintainers archived it. It is one of the most widely adopted component libraries in the Vue ecosystem, and a very large number of applications were left without a maintenance path.
When a dependency that central stops being maintained you have three options: freeze it and accumulate risk, rewrite your UI layer, or pick up maintenance. We went with the third, in the open rather than in a private fork. The same reasoning applies to anything else we take on.
Who is behind it
Engineers who know these libraries well. There is no company behind this and no funding.
That changes what we care about. We are not chasing feature announcements or trying to build a brand. The goal is to keep a widely used dependency stable for the people who rely on it.
How we approach it
- Compatibility over novelty. The component API matches PrimeVue 4.x. Migrating should be a dependency swap, not a rewrite.
- Stability first, growth second. Backlog and dependency currency come before new components.
- Own the full stack. We forked the theming engine and icon set too, so no critical piece resolves at runtime from a scope we do not control.
- MIT, permanently. Every release stays MIT. That is why the fork exists.
- Boring release engineering. Predictable, versioned releases with a changelog you can actually read.
Where things stand
OpenVue is at 1.0.0-rc.0, the release candidate for its first stable
release. The API is settled and the packages are on npm under the rc
dist-tag; current work is the existing issue backlog and the final checks before 1.0.0.
OpenIcons and OpenUXKit have both shipped 1.0.0 and follow semantic
versioning from here.
The roadmap and its progress live in the OpenVue README.
Contact
Day-to-day conversation happens on Discord. For anything else, email contact@openvi.dev or open an issue on the relevant repository under github.com/openvi-foundation. Security reports should follow the security policy rather than a public issue.
OpenVi Foundation is not affiliated with, sponsored by, or endorsed by PrimeTek Informatics or PrimeUI. All upstream work is attributed under its original MIT license.