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

platform-brand

v0.1.4

Published

Brand packs read by every platform repo: identity, hosts per stage, contacts, social handles, product names, colours and art.

Readme

platform-brand

Brand packs read by every platform repo: identity, hosts per stage, contacts, social handles, product names, colours and art.

Generated from brand/packs.json in trastienda/marketing; do not edit a published copy. The source of every value and the schema are brand/*.json and scripts/brand-contract.mjs there.

Packs: ficticia (a fake brand for rebrand proofs), trastienda. Default: trastienda.

import { brand, getPack, hosts, origin, literals, socialUrl, art } from 'platform-brand';
brand.name;                         // BRAND=<slug> selects the pack in Node; a bundler calls getPack(slug)
hosts('dev').api;                   // a hostname, or null where the stage has none
origin('app', 'prod');              // https://…
literals();                         // { current, legacy } for a literal lint
art('markCurrentColor').svg;        // inline markup; files at platform-brand/packs/<slug>/art/<role>.svg

For servers that only need identity, hosts, contacts, colours and the other brand data:

import { brand, getPack, hosts, origin, literals, socialUrl } from 'platform-brand/data';
// CommonJS: const { brand, hosts } = require('platform-brand/data');

The /data entry exports the same helpers, packs, DEFAULT_PACK and STAGES, but omits art, logos and the art() helper. It is a standalone module with no import of the main entry or SVG files. Both entries use the same publishable packs and BRAND selection, including the fixture pack; choosing /data does not exclude fixtures. ESM and CommonJS each have matching TypeScript declarations. The main entry retains its artwork API.

Entry sizes

Exact generated UTF-8 bytes, before consumer bundling; gzip uses level 9. These are module sizes, not whole-package download sizes. The tarball still includes artwork for main-entry consumers.

| Module | Bytes | Gzip bytes | |---|---:|---:| | index.mjs | 36509 | 6680 | | index.cjs | 36531 | 6698 | | data/index.mjs | 8718 | 2515 | | data/index.cjs | 8740 | 2531 |