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

@kosko-app/design-tokens

v0.2.0

Published

Kosko's design system for every repo that draws Kosko UI: the resolved colour, scale and font tokens, every icon glyph, and the design-system check that keeps raw values out. Generated from content-vault's design/ — one source.

Readme

@kosko-app/design-tokens

Kosko's design system, for every repository that draws Kosko UI:

  • TOKENS (@kosko-app/design-tokens): every colour role resolved to a literal, per surface (app, popup) and theme (light, dark), plus the scale (spacing, type, radius, icon sizes) and the fixed document / content colours. Deep-frozen.
  • tokens.css (@kosko-app/design-tokens/tokens.css): the same roles as CSS custom properties, light and dark (prefers-color-scheme, with an explicit data-theme="light|dark" on :root winning).
  • tokens.json: the resolved values as JSON, for a consumer that is not JavaScript.
  • ICONS / ICON_PROFILES (@kosko-app/design-tokens/icons): every glyph by meaning (note, trash, move-to-notebook, …) as [[tag, attrs], …] on a 24 grid, and how each platform strokes it. Each glyph is also a standalone SVG: @kosko-app/design-tokens/icons/<meaning>.svg.

Every file under generated/ is produced from design/ in the content-vault repository by npm run tokens and npm run icons. Do not patch it: a change is an edit to design/ there, then a package release.

Use

import { TOKENS } from '@kosko-app/design-tokens';
const accent = TOKENS.app.light.acc;
@import '@kosko-app/design-tokens/tokens.css';
.button { background: var(--acc); color: var(--on-acc); padding: var(--space-2) var(--space-3); }

Pin it exactly ("@kosko-app/design-tokens": "0.1.0", never a range): a design change reaches a consumer only when that consumer bumps the pin.

The design-system check

kosko-ds-check keeps raw colours, font names, typed sizes and hand-drawn icons out of a repo's UI code. Describe the repo in a kosko-ds.config.json at its root:

{
  "channels": { "cli": { "dirs": ["src", "bin"], "extensions": [".mjs", ".html"], "platform": "web" } },
  "exempt": [{ "path": "src/vendor.mjs", "reason": "third-party code keeps its own look" }],
  "baseline": "design/system-baseline.json"
}

then run kosko-ds-check (the whole tree) or kosko-ds-check src/page.mjs (some files). Exit 0: clean. Exit 1: every new violation, with file, line, the literal and the token to use. Exit 2: a config or usage error. platform: "native" gives React Native rules and hints. The same check is importable from @kosko-app/design-tokens/check (loadConfig, createCheck, runGate).

Releases

Published from content-vault by GitHub Actions through npm's trusted publishing, staged and approved by the owner with 2FA. No provenance attestation: the source repository is private.

Requirements

Node 22 or later, ES modules. No runtime dependencies.

Licence

Apache-2.0. The utility glyphs are drawn by lucide (ISC); their notice is in generated/LICENSE-lucide.txt.