@vernostudio

Promising 62/100 · #150 of 342 scored

The full OKLCH scale plus every variable shadcn components read, so anything you install lands on the same tokens instead of its own colors.

@vernostudio is a shadcn UI community registry. Its source repository is verno-studio/website , which has 2 GitHub stars, 2 forks and 3 contributors. The last commit was 48d ago (36 commits in the last 90 days). The latest release is @vernostudio/cli@0.2.2. It scores 62/100 on Sealambda's maturity index, placing it in the Promising tier.

Scoring

Maturity breakdown

62 / 100 · Promising

0avoid · 305080 · reliable100

new confidence 87% · weight backed by data

Maintenance ×35% 82 → +32.8

last commit 48d ago · 36 commits/90d · solo maintainer

Popularity ×20% 15 → +3.4

2★ · 2 forks

Community ×20% 37 → +8.6

3 contributors · bus factor 1 · 0 watching

Responsiveness ×13% N/A — excluded

only 2 issues — too few to rate

Hygiene ×12% 100 → +13.8

MIT · 100% health files

Signals

Repository facts

2
Stars: 2
Forks: 3
Contributors: 1
Bus factor: 0
Open issues: 2
Closed issues: 36
Commits (90d): TypeScript
Language: MIT
License: @vernostudio/cli@0.2.2
Latest version: 10
Releases: 48d ago
Last commit

Classification

License, pricing and purpose

License: MIT · ✓ OSI-approved; Permissive: Use, change and redistribute freely, keeping the notice.
Access: FOSS; An OSI-approved or FSF-libre license, and everything offered is free.
Purpose: A small registry providing a shared OKLCH color theme and a handful of utility UI items like a file tree and JSON viewer for shadcn/ui.
Commercial model: Free; Everything the project offers is free to use, with no paid tier. Donations and sponsorships do not count as paid.
Tied to a service: No; Yes when the components are a client for a commercial API or service.
Scope: Utilities; Supporting items without a component set: hooks, libraries, icons or logos, themes, fonts or tooling.
Domains: Theming; Theming: Themes, color systems, fonts and theme generators.
Design: Themed; Keeps the shadcn/ui structure but ships its own tokens (colors, radius, fonts, shadows), so it reads as a branded variant.
Coverage: 3%; Share of shadcn/ui core primitives that the registry ships.
Design distance: 0.87; Measured on sample items: 0 is identical to vanilla shadcn/ui, 1 is entirely different.

Evidence

“The Verno Studio component registry. Install any of it into your own project with the shadcn CLI.”
commercial · homepage ↗
“The part of this design system that is meant to travel, published as a shadcn registry. The components on this site stay here. What is worth sharing is the palette underneath them”
scope · homepage ↗
“Theme The color scale plus the variables shadcn components read, so a component from either registry agrees with the other on what --background means.”
domains · homepage ↗
“The color scale plus the variables shadcn components read, so a component from either registry agrees with the other on what --background means.”
design · homepage ↗

AI-suggested by google/gemini-3.8-flash@Google AI Studio on 2026-10-02

Usage

Install

Add components from this registry with the shadcn CLI (configure the registry URL in your components.json):

pnpm dlx shadcn@latest add @vernostudio/[component]

endpoint: https://verno-studio.vercel.app/r/{name}.json

Homepage ↗ GitHub ↗

README

Embed the maturity badge

Add a live maturity badge to your README:

[![shadcn maturity](https://shadcn.sealambda.com/badge/vernostudio.svg)](https://shadcn.sealambda.com/registry/vernostudio/)

Other Promising registries

← all registries