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

@amansanoj/brand

v1.0.4

Published

Personal brand system — shadcn/ui-compatible CSS tokens, Tailwind config, logos, fonts, headshots, and shared assets used across all my projects.

Readme

OG Image

Contents

  • globals.css — CSS custom properties for light & dark mode (shadcn/ui convention)
  • tailwind.config.ts — Tailwind config wired to CSS variables
  • tokens.json — machine-readable token reference (light + dark)
  • assets/ — logo SVG
  • images/ — headshots, open graph images

Tokens

All colors are defined as oklch CSS custom properties. Key values:

| Token | Light | Dark | |---|---|---| | --primary | oklch(0.5183 0.137 249.921) | oklch(0.5183 0.137 249.921) | | --accent | oklch(0.7415 0.135 58.279) | oklch(0.7415 0.135 58.279) | | --background | oklch(1 0 0) | oklch(0.2134 0 0) | | --foreground | oklch(0.2134 0 0) | oklch(1 0 0) | | --radius | 0.5rem | 0.5rem | | Font sans/serif | Rubik | — | | Font mono | JetBrains Mono | — |

See globals.css for the full token list.

The original hex palette is also preserved in tokens.json under color.palette for use outside of CSS contexts:

| Key | Value | |---|---| | color.palette.primary.default | #156bb3 | | color.palette.primary.light | #3d8fd1 | | color.palette.primary.dark | #0e4f87 | | color.palette.accent.default | #ea944c | | color.palette.accent.light | #f0b07a | | color.palette.accent.dark | #c8712a |

Usage

Install in a project:

bun add @amansanoj/brand

1. Import CSS variables

In your project's global stylesheet (e.g. app.css / globals.css):

@import '@amansanoj/brand/globals.css';

This sets all --token custom properties on :root (light) and .dark (dark mode).

2. Add the Tailwind config

In your project's tailwind.config.ts:

import type { Config } from 'tailwindcss'
import brand from '@amansanoj/brand/tailwind'

const config: Config = {
  ...brand,
  content: ['./src/**/*.{ts,tsx,svelte}'],
  theme: {
    ...brand.theme,
    extend: {
      ...brand.theme?.extend,
      // project-specific overrides here
    },
  },
}

export default config

All color utilities (bg-primary, text-foreground, border-border, etc.) will resolve to the CSS variables automatically.

3. Import assets

import headshot from '@amansanoj/brand/images/headshots/main.jpg'

Fonts

globals.css already imports Rubik and JetBrains Mono from Google Fonts. No additional <link> tags needed.