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

@21stgov/commons-tokens

v0.6.0

Published

Design tokens for Commons, the accessibility-first design system for U.S. local governments. DTCG JSON sources compiled to CSS custom properties with a mathematically guaranteed color-contrast contract.

Readme

@21stgov/commons-tokens

Design tokens for Commons, the accessibility-first design system for U.S. local governments. DTCG JSON sources → Style Dictionary → CSS custom properties (--cui-*) + resolved JSON.

The grade contract (the whole point)

Every color is named {family}.{grade} (families: gray, blue, indigo, cyan, green, gold, orange, red, violet; grades 5–90). Each grade is pinned to a fixed WCAG relative-luminance target that is identical across families, so grade arithmetic predicts contrast for any two colors, even across families:

| Grade delta | Guaranteed contrast | WCAG use | | ----------- | ------------------- | -------- | | ≥ 40 | ≥ 3:1 | Large text, UI components, focus indicators (AA) | | ≥ 50 | ≥ 4.5:1 | Normal text (AA) | | ≥ 70 | ≥ 7:1 | Normal text (AAA / high-contrast theme) |

Grade 50 additionally clears 4.5:1 against both pure white and pure black. The generator (scripts/generate-palette.ts) binary-searches OKLCH lightness to hit each grade's luminance target in the shipped hex values, and pnpm validate:contrast re-derives WCAG math independently and re-checks every pair (1,700+ checks) from the built output. If it exits 0, the contract holds — pick colors by arithmetic, not by eyeballing.

Usage

@import '@21stgov/commons-tokens/index.css';

Themes: :root/[data-theme='light'] is the default; [data-theme='dark'] and [data-theme='high-contrast'] remap the same semantic variables (--cui-text-default, --cui-bg-default, --cui-focus-ring, …), with prefers-color-scheme / prefers-contrast fallbacks for visitors who never chose a theme.

Tailwind v4

@import '@21stgov/commons-tokens/tailwind.css'; (after tailwindcss and index.css) — an @theme inline bridge mapping every semantic variable to shadcn-style tokens (bg-background, text-foreground, bg-primary, ring-ring, state trios like bg-error/text-error-foreground/border-error-border) plus the full primitive palette, spacing, type, radius, shadow, and easing scales, all as var(--cui-*) references so runtime data-theme switching keeps working. Tailwind's stock color palette is reset (--color-*: initial) so only contract-checked Commons colors exist, and the build fails if a semantic variable ever drifts out of the bridge (pnpm validate:tailwind compile-checks the shipped file).

Scripts

  • pnpm generate — regenerate src/tokens/color.primitives.tokens.json (deterministic; the result is committed source — run this only when the generator changes, then commit the diff)
  • pnpm build — compile the committed token sources to dist/
  • pnpm validate:contrast (= pnpm test) — independent WCAG audit of dist/