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

palette-lab

v0.0.0

Published

Analyze the hell out of your color tokens

Readme

Palette Lab

Toolkit for analyzing color palettes.

Palette Stats

Given an object literal of palettes → color names → tints → colors, easily calculate any stats you need about about the color components. Pretty print the results or import them in other scripts for further processing. The palettes need to all use the same tints and color names ("hues") otherwise results will be meaningless.

Usage

You can use this as a JS library or as a CLI tool.

As a JS library

import { getStats } from "palette-lab";

// Your palette data
import palettes from "./palettes.js";

getStats(palettes);

This will print out sample stats to the console (oklch coordinate ranges). However, to really harness the power of this library, you should provide your own queries.

import { getStats } from "palette-lab";

// Your palette data
import palettes from "./palettes.js";

// Your queries
import queries from "./queries.js";

getStats(palettes, queries);

As a CLI tool

pstats 'palettes/*.css' 'queries/*.js'

Palette Queries

Each query consists of the following params to analyze:

  • component: The color component to analyze (h, c, l). If getValue() is provided, this is ignored.
  • getValue: A function to extract the value to analyze from a color, for more complex analysis than just getting a component
  • by: The grouping to analyze by (1-2 of 'tint', 'hue', 'palette'). If getKey() is provided, this is ignored
  • getKey: A function to generate a key for each group. If not provided, it is generated based on the 'by' param
  • caption: The caption to display in the console. If not provided, a default label is generated from test params.
  • filter: Restrict to specific hues/tints/palettes or exclude them
  • stats: The stats to calculate for each group (min, max, mid, extent, avg, median, count)

When using as a CLI tool, all params can be specified as --param=value, except filters which are just included raw in the command.