unovue/shadcn-vue

Vue port of shadcn-ui

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 5th, 2026
Created on June 26th, 2023
Open Issues & Pull Requests: 140 (+0)
GitHub issues: Enabled
Number of forks: 678
Total Stargazers: 10,565 (+0)
Total Subscribers: 37 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

shadcn-vue is a component library that ports the design and approach of shadcn-ui to Vue, providing a collection of accessible, customizable UI components built on Radix Vue primitives.

The project addresses the need for a Vue-native alternative to shadcn-ui, which originated in the React ecosystem. Rather than distributing components as a traditional npm package, shadcn-vue provides copy-paste component code that developers integrate directly into their projects. This approach gives developers full ownership of the component source, enabling them to customize styling, behavior, and structure without being constrained by a locked dependency. The components are built on Radix Vue, which supplies unstyled, accessible primitives that the library layers with styling and additional functionality.

Developers should adopt shadcn-vue if they work in Vue and want a starting point for building a custom component library rather than relying on a pre-packaged solution. The project suits teams that need accessible, well-designed components but require the flexibility to modify them for brand consistency or specific requirements. The copy-paste model means you maintain your own component code, which trades the convenience of automatic updates for complete control and transparency.

The project maintains active development with regular commits across its codebase. Pull requests receive timely review and feedback from maintainers. The team responds consistently to issues raised by users, addressing questions and bug reports. Documentation is kept current alongside code changes, ensuring that guides and examples reflect the actual state of the library.