huntabyte/shadcn-svelte

shadcn/ui, but for Svelte. ✨

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 7th, 2026
Created on May 16th, 2023
Open Issues & Pull Requests: 128 (+0)
GitHub issues: Enabled
Number of forks: 568
Total Stargazers: 9,099 (+0)
Total Subscribers: 50 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.2 hours
Mean response time: 10.9 days
90th percentile: 14.3 days
Tracked items: 577

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 4 hours, while "cli" waits about 32 hours. 59% of tracked open issues have had no activity in three months. Only 10% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 67
New in 7 days: 3
Closed in 7 days: 4
Avg open age: 264 days
Stale 30+ days: 58
Stale 90+ days: 44

Recent activity

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

Top labels

  • triage (249)
  • docs (59)
  • feature (55)
  • contributions welcome (51)
  • bug (47)
  • cli (28)
  • awaiting submitter (13)
  • parity (13)

Detailed Description

shadcn-svelte is a component library that brings the shadcn/ui design system to Svelte applications. It provides accessible, customizable components that developers can copy and paste directly into their projects, built on Svelte and Tailwind CSS.

The project addresses the need for a Svelte equivalent to shadcn/ui, which was originally designed for React. Rather than installing components as dependencies, shadcn-svelte follows the copy-paste approach, allowing developers to own and customize each component in their codebase. This strategy means you get full control over component behavior and styling without being locked into a specific library version or API.

Developers should choose this tool if they are building Svelte or SvelteKit applications and want a modern, accessible component foundation with the flexibility to modify components as their project evolves. The copy-paste model suits teams that prefer to maintain their own component implementations rather than depend on external packages. This approach works well for building custom component libraries tailored to specific design systems or brand requirements.

The project maintains active community engagement through a Discord server and accepts contributions from multiple developers. Development is distributed across several maintainers who collaborate on expanding the component collection and keeping the library aligned with Svelte ecosystem updates, including support for newer Svelte versions.