npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

brutalkit

v0.4.0

Published

A tokens-first design system built on shadcn/ui

Readme

Brutalkit

A tokens-first design system built on shadcn/ui. Thick borders, hard-edge shadows, OKLCH color tokens, and Phosphor icons.

Storybook

Install

npm install brutalkit

Peer dependencies:

npm install react react-dom @phosphor-icons/react tailwindcss

Setup

Import the stylesheet after Tailwind in your app's CSS:

@import "tailwindcss";
@import "brutalkit/styles";

That is all that is required. Brutalkit tells Tailwind where to find its own compiled components, so component utilities are generated automatically — you do not need to add a @source directive yourself.

Optionally opt in to the global resets, which set the body background and foreground and the default border color on every element:

@import "brutalkit/preflight";

These are not applied by brutalkit/styles, so dropping brutalkit into an existing app does not change that app's baseline.

Add fonts (or use your own):

@import "@fontsource-variable/fraunces/opsz.css";
@import "@fontsource/geist-sans";
@import "@fontsource/jetbrains-mono";

Set a theme on your root element:

<html data-theme="sage">

The theme attribute must live on <html> (or be applied via ThemeProvider, which does this for you). Components like Dialog, Select, and Tooltip portal their content to document.body, so a theme scoped to a nested wrapper leaves that portalled content with no tokens — panels render transparent.

Themes

Five theme families, each with light and dark modes. All share the same ochre --brand; each family sets its own neutral --accent for hover and highlight surfaces.

| Theme | Vibe | Radius | |-------|------|--------| | sage | Clean stone neutral | 4px | | frost | Cool blue-gray | 4px | | ink | Max contrast black/white | 4px | | paper | Restrained warm | 4px | | midnight | Deep indigo | 12px |

Toggle dark mode by adding the dark class:

<html data-theme="frost" class="dark">

ThemeProvider

Use the built-in provider for runtime switching:

import { ThemeProvider } from "brutalkit";

function App() {
  return (
    <ThemeProvider defaultFamily="sage" defaultMode="system">
      {/* ... */}
    </ThemeProvider>
  );
}
import { useTheme } from "brutalkit";

function ThemeSwitcher() {
  const { family, setFamily, mode, setMode } = useTheme();
  // ...
}

Usage

Components use deep imports — no barrel file:

import { Button } from "brutalkit/button";
import { Card, CardHeader, CardTitle, CardContent } from "brutalkit/card";
import { Input } from "brutalkit/input";

Components

80+ components including all shadcn/ui primitives plus:

  • Layout: Sidebar, Resizable, ScrollArea, Separator
  • Data: Chart, DataTable, Heatmap, JsonViewer, PartitionBar, Table, Timeline
  • Feedback: Sonner, Spinner, DotMatrix, StatusIndicator, StatusMonitor, SystemBanner
  • Forms: Combobox, DatePicker, MultiSelect, InputGroup, InputOTP, NativeSelect, Field, Slider, Switch
  • Media: Carousel, VideoPlayer, Marquee, SpinningCircularText
  • Actions: Button, ButtonGroup, CopyButton, SlideToUnlock, Toggle, ToggleGroup
  • Overlay: Dialog, Drawer, Sheet, AlertDialog, ContextMenu, DropdownMenu, HoverCard, Popover, Tooltip
  • Display: Avatar, Badge, Card, Kbd, Marker, Bubble, TransportBadge, FlipClock, Empty

Browse them all in the Storybook.

Styling

  • All colors use semantic tokens (bg-primary, bg-muted, text-foreground) backed by OKLCH CSS variables
  • --brand is the ochre and is identical in every theme and mode — use it for CTAs and branded active states. --accent is a subtle per-theme neutral for hover and highlight surfaces, not a brand color
  • Interactive surfaces use border-2 by default
  • Hover lift (shadow-brutal + translate) on primary action buttons only
  • Custom shadows registered as Tailwind theme tokens: shadow-brutal, shadow-brutal-lg

Individual theme imports

If you only need specific themes:

@import "brutalkit/themes/sage";
@import "brutalkit/themes/frost";

Development

pnpm storybook          # component workbench on :6006
pnpm test               # vitest + storybook; a11y violations fail the run
pnpm check:stories      # every component has a story with real coverage
pnpm audit:visual       # contrast / overflow / focus audit, 5 themes x 2 modes
pnpm verify:consumer    # proves a fresh install produces styled components

verify:consumer builds a throwaway app against the packed library and fails if the shipped stylesheet stops generating component utilities. Run it before publishing.

License

MIT