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

@openbrf/tokens

v1.1.0

Published

The Open BRF design token contract, its default theme and the stylesheet built from it.

Readme

@openbrf/tokens

The design token contract of Open BRF: every token a theme can set, the default theme, Porttavlan, and the functions that resolve a token set and build the stylesheet from it.

The contract is versioned with semver, independently of the application.

Installing

npm install @openbrf/tokens

A theme is data, not code, so a theme author usually reaches this package through @openbrf/theme-tools, which depends on it. A plugin's view styles itself with the CSS custom properties the contract names, which the instance already serves.

What it exports

  • TOKENS, TOKEN_NAMES and REQUIRED_TOKEN_NAMES: the contract, one definition per token, and cssVariableName for the custom property each one becomes.
  • PORTTAVLAN_LIGHT and PORTTAVLAN_DARK: the default theme's two token sets.
  • resolveTokens(theme, inheritFrom): merges a partial token set over the one it inherits from and reports what was derived and what is still missing.
  • buildThemeStylesheet({ light, dark }): the stylesheet an instance serves, with light on :root, dark for a system that asks for it, and an explicit choice winning in both directions.
  • checkContrast, contrastRatio and CONTRAST_PAIRS: the WCAG contrast checks the theme lint applies, text at AA_CONTRAST_RATIO (4.5:1) and control borders at NON_TEXT_CONTRAST_RATIO (3:1).
import {
  buildThemeStylesheet,
  PORTTAVLAN_DARK,
  PORTTAVLAN_LIGHT,
} from "@openbrf/tokens";

const css = buildThemeStylesheet({
  light: PORTTAVLAN_LIGHT,
  dark: PORTTAVLAN_DARK,
});

Documentation

Licence

AGPL-3.0-only, with the Open BRF Module Exception. A theme or plugin view written against the token contract is a module under that exception and may be licensed on any terms. Both texts are in the package.