tusen-ai/naive-ui

A Vue 3 Component Library. Fairly Complete. Theme Customizable. Uses TypeScript. Fast.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 3rd, 2026
Created on June 4th, 2021
Open Issues & Pull Requests: 702 (+0)
GitHub issues: Enabled
Number of forks: 1,854
Total Stargazers: 18,535 (+0)
Total Subscribers: 99 (+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)

Open issues: 336
New in 7 days: 4
Closed in 7 days: 2
Avg open age: 520 days
Stale 30+ days: 306
Stale 90+ days: 290

Recent activity

Opened in 7 days: 3
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • feature request (507)
  • untriaged (358)
  • waiting for response (104)
  • pr welcome (102)
  • bug (59)
  • consideration-needed (31)
  • priority: low (18)
  • good reproduction ✨ (15)

Detailed Description

Naive UI is a Vue 3 component library that provides a comprehensive set of UI components built with TypeScript and designed for fast performance.

The library addresses the need for a complete, production-ready component collection in Vue 3 projects. It offers more than ninety treeshakable components covering common UI patterns, eliminating the need to build or source components individually. The theme customization system is built on TypeScript and requires only a JavaScript object for overrides, without depending on preprocessors or webpack loaders. Performance is optimized through virtual list implementations in data components by default, and the entire codebase is written in TypeScript to integrate seamlessly with typed projects.

Naive UI suits developers building Vue 3 applications who want a cohesive, typed component system without external styling dependencies. It works well for projects where theme consistency matters and where bundle size concerns make treeshaking valuable. The library is particularly useful when you need comprehensive component coverage without the setup overhead of CSS preprocessors or additional build tooling.

The project maintains a substantial user base, with nearly all open issues originating from external adopters rather than the core team. Initial responses to issues and pull requests typically arrive within one to two weeks. The issue tracker is primarily populated with feature requests and items awaiting triage or user response, reflecting an active community engagement pattern.