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

cortena-design

v3.6.0

Published

Cortena design tokens — the single source of truth for the Ascendence AI visual language.

Readme

cortena-design

Design tokens for Cortena and Ascendence AI — the single source of truth for colour, type, spacing, radius, shadow, motion and chart palettes.

Intended consumers: cortena (cortenaweb, cortena-auth) and cortena-extensions (11 web apps). Wiring those apps up is out of scope for this package — see CONSUMING.md.

Build

pnpm install
pnpm check                   # fails if dist/ is stale
pnpm test --maxWorkers=2     # 278 tests
pnpm build                   # writes dist/
pnpm lint <path>             # fails on hard-coded values in a consuming app

Open dist/guide.html to see everything rendered, with contrast ratios computed live.

How it works

src/tokens/*.json is the only thing edited by hand. build/build.mjs validates it, enforces WCAG AA, and emits dist/. dist/ is committed, so consumers compile nothing.

The contrast gate fails the build. If a colour does not clear its threshold, do not lower the threshold — pick a nearer stop of the same hue, mark it $derived: true, and record the measured ratio in its $description.

Every semantic colour must declare $contrastAgainst or $decorative. Without that rule the gate is opt-in, and a token added without a declaration is checked by nothing.

The ramp gate fails the build too. The contrast gate is the wrong instrument for a sequential or diverging ramp — a ramp's low end means "near zero" and is supposed to recede into the canvas — so the ramps are checked for what they actually have to prove: one hue for sequential, monotone lightness, at least 0.06 OKLCH lightness between adjacent steps, and a genuinely neutral midpoint with opposed poles for diverging. Re-step a ramp that fails; do not relax the check.

The lint fails the build too. cortena-design-lint reports every hard-coded value a token exists for, and every var() that does not resolve — with the nearest token and its value, computed from dist/tokens.css rather than a table. It walks .css, .tsx, .jsx and, since 3.3.0, .ts. Suppressing a line requires a reason. See LINTING.md.

See CONSUMING.md for how other repos pull this in, and CHANGELOG.md for what changed in each release from 3.4.1 on (earlier ones are in the git log).