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

@openref/theme-telltale

v0.1.0

Published

Second reference theme: monospace, a fixed grid, provenance readable in monochrome

Readme

@openref/theme-telltale

The second reference theme for OPENREF: an instrument rather than a document.

Everything is monospace. Every row sits on a 21 px grid. Provenance is a three letter code, DCL, DRV or INF, with an edge style behind it, so where a fact came from survives a monochrome print and reaches a screen reader as text. A bench line across the bottom says what the page weighs.

It is a level 2 theme, per SPEC 10.1: its own layout, all 21 positions of the frozen registry, all 122 tokens of the design contract in both colour modes, and its own faces. It reads @openref/vue and nothing else of this project: the four IR types the contract's props are declared in came onto that surface with T031-R1, and the @openref/core dependency this package used to carry for them came off.

Install

npm install @openref/theme-telltale @openref/vue

Use

import { telltale, TELLTALE_STYLESHEETS } from '@openref/theme-telltale';

// The stylesheets, in the order they must be applied: faces, tokens, rules.
TELLTALE_STYLESHEETS;

// The theme itself, as data.
telltale;

The three stylesheets resolve through this package's exports from anywhere:

  • @openref/theme-telltale/fonts.css
  • @openref/theme-telltale/tokens.css
  • @openref/theme-telltale/theme.css

Colour scheme

The dark values apply from prefers-color-scheme with nothing set, because a reader who has told their operating system they want a dark interface has answered the question. A host that has to force one sets data-oref-color-scheme="light" or "dark" on the document or on a subtree; that comes last in the stylesheet, so it wins on equal specificity rather than fighting the media query.

Under prefers-reduced-motion: reduce both durations collapse onto the zero token. That happens in the token layer rather than in this theme's rules, so a checker can read that it happened.

Fonts

JetBrains Mono for the interface at 400 and 700, Martian Mono for strip headings and the bench line at 700. Self hosted, no CDN, no external request of any kind. Each face is two files, latin and latin-ext, chosen by unicode-range. The complete OFL text of both families, a NOTICE.md and a manifest recording the source and digest of every byte travel in fonts/ inside the tarball.

What this package is for

It is the proof that the theme contract is real, and what that proof returned, including the parts that came back negative, is in THEME-BOUNDARY.md beside this file. Read it before writing a theme of your own: it is the list of things the contract does not yet carry.