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

@tfrc/foundation

v1.1.0

Published

Color ramps, spacing base, reset, and the token contract. No user-facing components. Consumed by @tfrc/marketing and @tfrc/product — never the other way around.

Readme

@tfrc/foundation

Ships no user-facing CSS directly. Consumed by @tfrc/marketing and @tfrc/product, and therefore installed transitively by every consumer — which is why the consumer-side checker lives here rather than in a fourth package (decisions/0009.md).

Contains:

  • bin/tfrc-verify.js — the check a consumer runs on itself, via npx tfrc-verify. Enforces one-dialect-only, pinned versions, no raw color values, and the reserved gain/loss colors, in repositories this one cannot see. Tested by scripts/test-verify-consumer.js.
  • src/palettes/meridian.css — the active v1 palette (raw ramps only)
  • src/palettes/{lilac,meadow,daylight}.css — designed alternates, not wired into any shipped package. See decisions/0003.md.
  • src/base.css — reset, focus-visible, reduced-motion, the 4px spacing scale, and shared easing curve shapes (not durations — those diverge per package, see decisions/0004.md).
  • src/index.css — imports the active palette + base, in that order.

Does not contain semantic tokens (--color-accent and friends) or any component. See CONTRACT.md for what every consumer must define, and decisions/0004-token-contract-not-shared-values.md for why the contract lives here but the values don't.

To change the active palette, do not edit this package — point @tfrc/marketing's and @tfrc/product's tokens.css imports at a different palette file, and update STATE.md.