About
A design system for Vue 3, made by one person, in the open, with the weak spots named on this page rather than discovered later.
What this is
Components, foundations and the UnoCSS preset that ties them together. The name is the architecture: you name the components you render, and the build gives you exactly their CSS and their graph — not a barrel, and not a promise about tree-shaking.
Who makes it
One maintainer, Evgeniy Fureev. There is no company behind the project, no team, no paid support and no service-level promise. That is a fact worth knowing before you adopt it, not after.
What holds the quality instead
Machinery. One person cannot review two hundred pages before every release, so the review is encoded: figures about the product are generated rather than typed, the component registry comes from the package, the token tables come from its JSON, and the reference from its `exports`. Anything typed by hand that could drift is checked by a gate that fails the build.
30 build gates run on every push, plus accessibility and performance checks in a real browser. A gate that only warns is not a gate.
Where the project is weak
The same three named on the comparison pages, because a weakness that is only admitted where nobody looks is not admitted.
Immature
Version 0.41.0, before 1.0. Breaking changes happen and live in the changelog; there is no migration guide yet because there has been nothing to migrate from.
One maintainer
No company behind it, no paid support, no service-level promise. What holds quality instead is machinery: twenty-seven build gates that fail the build rather than file a warning.
A non-standard licence
Apache-2.0 with an ethical use clause. That makes it source-available rather than OSI-approved open source, and a licence register may treat it as unknown. For the overwhelming majority of commercial uses there is no restriction at all — but read it before you plan around it.
Where to ask
Questions and ideas go to the repository discussions: an answer there is indexed and stays useful to the next person. Security reports have their own address and their own rules.
Discussions on GitHubReporting a vulnerabilityHow to contribute