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

@tangle-network/brand

v0.2.0

Published

Tangle brand system — design tokens, logo, Tailwind v4 theme. Single source of truth for every Tangle app.

Readme

@tangle-network/brand

Single source of truth for the Tangle design system. Design tokens, logo, and a Tailwind v4 theme preset, shared across every Tangle app (tangle-website, sandbox-ui, evals, agent-builder, product surfaces).

Scope: tokens, not components. Components live in @tangle-network/sandbox-ui.

Install

pnpm add @tangle-network/brand

Use

Tailwind v4 app

/* app.css */
@import "@tangle-network/brand/styles";
@import "tailwindcss";

That single import wires:

  • CSS custom properties for dark (:root) and light ([data-sandbox-theme="vault"])
  • Tailwind v4 @theme block so bg-brand, text-fg-muted, rounded-lg, font-display, etc. just work
  • Base styles and a handful of utility classes (.text-gradient-brand, .depth-1..4, .status-dot-*)

Fonts are not bundled — see Fonts below.

Finer control

@import "@tangle-network/brand/styles/tokens";
@import "tailwindcss";
@import "@tangle-network/brand/styles/theme";
@import "@tangle-network/brand/styles/globals";

Logo

import { Logo, TangleKnot } from "@tangle-network/brand";

<Logo size="lg" />
<Logo size="md" suffix="Sandbox" />
<TangleKnot size={48} />

What's in the palette

  • Accent — indigo #6366F1 / #818CF8 / #A5AAFC
  • Depth stack#0C0B1D#262448 (dark); #f4f4f9#dcdbe8 (light)
  • Status — emerald / amber / coral for running / stopped / error
  • Radii — 6/8/12/16px (dark); 2/4/6/8px (light/"vault")

Light theme activates via data-sandbox-theme="vault" on a parent element.

Fonts

brand references the following font families in its design tokens but does not bundle them — consumer apps must load the fonts themselves. This is deliberate:

  • (a) @import url(...) inside library CSS breaks downstream when CSS chain-imports get reordered — once the dist CSS is inlined after any rule, the URL @import is no longer at the top of the merged stylesheet, the CSS spec disallows it, and PostCSS rejects the build. Mirrors tangle-network/sandbox-ui#28.
  • (b) Shipping a third-party Google Fonts request from a library is privacy-hostile.
  • (c) Consumers cannot fall back when the network fails.

| Family | Role | Used as CSS variable | | ------------ | ----------------------------------- | -------------------- | | Geist | UI body text (dark) | --font-sans | | Geist Mono | Code, terminal | --font-mono | | Outfit | Display / headings (dark) | --font-display | | Manrope | Display / headings (vault) | --font-display | | Inter | UI body text (vault) | --font-sans |

Pick one loading strategy that fits your app:

1. Self-hosted via @fontsource/* (recommended — no external network request):

pnpm add @fontsource/geist-sans @fontsource/geist-mono @fontsource/outfit @fontsource/manrope @fontsource/inter
// app entry
import "@fontsource/geist-sans/400.css";
import "@fontsource/geist-sans/500.css";
import "@fontsource/geist-sans/600.css";
import "@fontsource/geist-sans/700.css";
import "@fontsource/geist-mono/400.css";
import "@fontsource/geist-mono/500.css";
import "@fontsource/outfit/500.css";
import "@fontsource/outfit/700.css";
import "@fontsource/manrope/500.css";
import "@fontsource/manrope/700.css";
import "@fontsource/inter/400.css";
import "@fontsource/inter/600.css";

2. Google Fonts via HTML <link>:

<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link
  rel="stylesheet"
  href="https://fonts.googleapis.com/css2?family=Geist:wght@300;400;500;600;700&family=Geist+Mono:wght@400;500;600&family=Outfit:wght@400;500;600;700&family=Manrope:wght@400;500;600;700;800&family=Inter:wght@400;500;600;700&display=swap"
/>

Any family you omit falls back per the --font-* token chain.

Policy

  • No additions without a cross-app audit. New tokens land here or nowhere; do not fork this into apps.
  • Version as a product. Semver. Breaking token changes are major bumps.
  • Sandbox-ui as the stress-test surface. Tokens ship here only after sandbox-ui has used them in anger.

Development

pnpm install
pnpm build

To iterate inside a consuming app, link locally:

# in ~/webb/brand
pnpm link --global

# in the consumer
pnpm link --global @tangle-network/brand

Or use a file: path dependency ("@tangle-network/brand": "file:../brand").