Library / SDK
unovue/inspira-ui avatar
unovue/inspira-ui

Inspira UI is a Nuxt site full of components you copy into your app

Build beautiful website using Vue & Nuxt.

5,095 stars354 forksVueMIT

At a glance

What is it?
Inspira UI collects Vue and Nuxt components inspired by Aceternity UI and Magic UI and publishes them as source you adapt, not as a package you install. The repository is really the documentation site, built on Nuxt Content, with a component registry built by a script.
Who is it for?
Inspira UI fits a Vue or Nuxt team that wants a specific animated component and is willing to own the source afterwards, and the documentation site at inspira-ui.com is where that work happens. It does not fit a team that wants a versioned dependency, an automated upgrade path, or a per component list of what it drags into the bundle.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 29 days ago.
What is it written in?
Mainly Vue, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • unovue/inspira-ui5,095 ★ · +89
Star history
Repository2026-09-232026-11-15
unovue/inspira-ui5k5.1k

89 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The repository is a Nuxt application, not a component package

The manifest gives the game away. The package is named `inspira-ui`, it is ESM, and its scripts are all Nuxt commands: `nuxt dev`, `nuxt build`, `nuxt generate`, `nuxt preview`, with `nuxt prepare` wired to `postinstall`. Nuxt itself is a dependency at a pinned 4.3.1. Alongside it sit `app/`, `content/`, `modules/`, `i18n/`, `public/`, `plugins/`, `registry/` and `utils/`, plus `nuxt.config.ts` and `content.config.ts`.

So what lives here is the documentation site and its source, with the components inside it. Nothing in this manifest publishes components to a registry for others to install. The one artefact under the project's own scope is the dependency `@inspira-ui/plugins` at `^0.0.2`, a 0.0.x version that npm treats as an early, unstable line. If you are evaluating this as a dependency to add to a package.json, that is the shape of it: one small plugins package, and everything else copied by hand.

Components are picked and adapted rather than installed

The project is explicit about not being a traditional component library. Its own words are that you pick, customize and adapt components as needed, and that it includes unique custom components contributed by the community and created by the authors. The distribution model follows from that: you take the source of a component into your project and own it from there.

The machinery behind the examples is a component registry. There is a `registry/` directory, a build script at `./scripts/build-registry.mts` run by `build:registry`, a `dev:registry` variant that points `REGISTRY_URL` at `http://localhost:3000/r`, and a final `build:copy` step that copies `public/_routes.json` into `dist`. A full build runs the registry build, then `nuxt build`, then that copy.

The consequence for a consumer is worth stating plainly. With no versioned package and no release tags, there is nothing to pin, nothing to upgrade and no changelog to read. When the project improves a component, picking up the change means comparing the new source with the copy you already own.

The dependency list is the real catalogue of components

Since the components are source rather than a package, the manifest is the best map of what they are built from. The animation entries are `gsap`, `motion-v`, `ogl` and `postprocessing`. The three-dimensional ones are `cobe`, `@splinetool/runtime` and `@tresjs/nuxt`, which brings a Three.js renderer with it. Smaller pieces include `@googlemaps/markerclusterer`, `canvas-confetti`, `@number-flow/vue`, `dotted-map` and `dialkit`, with `@vueuse/nuxt` for composition utilities and `clsx` plus `class-variance-authority` for class handling.

That list is also the warning. Several of those packages are large and animation oriented, so taking one decorative component can pull a graphics runtime into an application that has no use for it. This README does not publish a dependency footprint per component, and the configuration guide it points to is where the options for each one are described, not what each one costs you at build time. Decide on the dependency question before you copy, not after.

Two linters, prettier, and no test script at all

The tooling is doubled up on linting and has nothing on testing. Linting runs `oxlint .` and then `eslint .`, with a matching `lint:fix`, and formatting is `prettier . --check` with `prettier . --write` for the fix. Configuration files sit at the top level as `eslint.config.mjs`, `prettier.config.js` and `tsconfig.json`, and the editor setup lives in `.vscode/`.

The package manager is pinned rather than merely documented: `packageManager` is set to `[email protected]` with a lockfile hash, and `pnpm-lock.yaml` sits next to `pnpm-workspace.yaml`, so a workspace-aware pnpm is expected. What is absent matters as much: there is no `test` script in the manifest and no test runner among the visible dependencies. A project built on components copied from here is therefore verified in its own repository, with its own tests, because upstream will not run yours and does not run its own.

The documentation site and the components share one repository

The docs are a Nuxt Content application. `@nuxt/content` is pinned at 3.12.0, the content directory has its own `content.config.ts`, and the theme dependency is listed as `docus` at `latest`. Around it sit `@nuxt/icon` at 2.2.1, `@nuxt/image` at 2.0.0, `@nuxt/fonts` at 0.14.0, `@nuxt/scripts` at 0.13.2 and `nuxt-gtag`, so icons, images, fonts and analytics are all handled inside the site rather than by hand.

Localisation is part of the repository too. There is an `i18n/` directory and three readmes at the top level, `README.md`, `README_CN.md` and `README_IT.md`, for English, Chinese and Italian. The last push was on 2026-10-17 and the repository is not archived. One consequence of a single repository is that a documentation fix and a component rewrite travel the same commit stream, so the history of the site and the history of the components cannot be separated after the fact.

No releases means nothing to pin or to diff against

This repository has no GitHub releases. There are no tags to install from, no version history to read and nothing in the manifest that a consumer could depend on for the components themselves. The only published artefact referenced is `@inspira-ui/plugins` at `^0.0.2`, and a caret range on a 0.0.x version resolves inside that patch line rather than across minor versions.

That is workable for a copy-source project and awkward for a procurement conversation. If your team needs to say which version of a component you shipped, the answer has to come from your own repository and your own commit history, because upstream keeps none for you. The `CONTRIBUTING.md` file and the contribution guide linked from the README are the entry points for contributing, and sponsorship to the single maintainer is the funding route offered.

Adapted designs credit four upstream projects

The acknowledgements name where the visual work comes from. Aceternity UI is credited with providing the inspiration and permission to adapt the original designs. Magic UI is credited for design inspiration. shadcn-vue is credited as the Vue port of shadcn-ui and for contributions to some components, and shadcn-docs-nuxt is credited for the documentation site itself.

The repository itself is MIT licensed, which the README states as free and open source. What it does not do is restate the terms of the designs it adapted, so the licence you inherit for a copied component is the MIT file in this repository while the design it reproduces belongs to someone else. Teams shipping a product should read the upstream terms for the specific component they took rather than assume the repository licence covers the whole chain.

Editorial conclusion

Inspira UI fits a Vue or Nuxt team that wants a specific animated component and is willing to own the source afterwards, and the documentation site at inspira-ui.com is where that work happens. It does not fit a team that wants a versioned dependency, an automated upgrade path, or a per component list of what it drags into the bundle. Before adopting, check the MIT licence against the upstream projects the designs come from, read the per component configuration guide rather than the summary page, and expect to verify any copied component inside your own project, since this repository ships no tests and no releases.

Frequently asked questions

How do I install components from Inspira UI?

You do not install them as a package. The project describes itself as a collection of ready-to-use Vue components that you pick, customize and adapt, rather than a traditional component library, and the repository publishes no releases to install from. Examples and options live on the documentation site at inspira-ui.com.

Is Inspira UI compatible with Nuxt?

Yes. Nuxt compatibility is listed among the key features, the repository is itself a Nuxt 4.3.1 application with a nuxt.config.ts, and the components are offered for both Vue and Nuxt with a configuration guide for per component options.

What do Inspira UI components take from Aceternity UI and Magic UI?

The project says it brings the aesthetics and functionality of Aceternity UI and Magic UI to the Vue and Nuxt ecosystem, and the acknowledgements credit Aceternity UI with permission to adapt the original designs and Magic UI with design inspiration. shadcn-vue contributed to some components.

How do I run the Inspira UI repository locally?

It is a Nuxt app pinned to [email protected]. `pnpm dev` runs `nuxt dev`, and a full `pnpm build` runs the registry build script first, then `nuxt build`, then copies `public/_routes.json` into `dist`. Linting uses both oxlint and eslint, and formatting uses prettier.

Official sources

  1. Issues
  2. License: MIT
  3. Project website
  4. README
  5. unovue/inspira-ui on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/unovue-inspira-ui.svg)](https://hysenlabs.com/projects/unovue-inspira-ui)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/unovue-inspira-ui.svg)](https://hysenlabs.com/projects/unovue-inspira-ui)

Was this useful?