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

@noundry/nouns-assets

v1.17.1

Published

Nouns run-length encoded image data maintained by Noundry.

Readme

@noundry/nouns-assets

This is a drop-in replacement for @nouns/assets. It includes the Noundry-maintained snapshot of Nouns image data, with new package versions published when the asset data is updated.

Replacing @nouns/assets

Just install the package:

npm install @noundry/nouns-assets
yarn add @noundry/nouns-assets
pnpm add @noundry/nouns-assets

Uninstall @nouns/assets

npm uninstall @nouns/assets
yarn remove @nouns/assets
pnpm remove @nouns/assets

Now replace every @nouns/assets import in your app with @noundry/nouns-assets and you're good to go

Use hosted asset data

(Browser only, with no SSR support)

To receive the current Noundry-maintained asset snapshot without requiring package updates or new deployments, you can include the supplementary script in your app:

<script src="https://assets.noundry.wtf/nouns/image-data.js"></script>

This script injects the hosted asset data on window.nounsImageData for @noundry/nouns-assets to use.

you should include it before any other scripts, in html > head. that way, the hosted asset data will be available when your app loads. Noundry updates this hosted data manually when the package snapshot is refreshed.

e.g.:

<!-- Depending on your framework, this might be an index.html file, the global layout.tsx, etc -->
<html>
  <head>
    <script src="https://assets.noundry.wtf/nouns/image-data.js" />
    <!-- any other scripts ... -->
  </head>
  <body>
    <!-- the rest of your app... -->
  </body>
</html>

For debug purposes, you can also get the prettified version on https://assets.noundry.wtf/nouns/image-data.json

Development

Install dependencies

pnpm

Update image data

Fetch the current onchain trait counts, verify trait names, and regenerate src/image-data.json:

pnpm --filter @noundry/nouns-assets update:image-data

The command uses the trait names in packages/noggles/src/nouns/traitNames.json. It first fetches onchain trait counts. If new onchain traits do not have names yet, it appends placeholder names such as head-256 to traitNames.json and stops. Replace those placeholders with real trait names, then rerun the command. It will only fetch full artwork after the trait-name counts match onchain counts and no placeholders remain. If the generated src/image-data.json differs from the existing snapshot, the package patch version is bumped automatically.

You can set ETH_RPC_URL, MAINNET_RPC_URL, ALCHEMY_API_KEY, or NEXT_PUBLIC_ALCHEMY_API_KEY if you want to use a specific mainnet RPC provider.

Usage

Access Noun RLE Image Data

import { ImageData } from "@noundry/nouns-assets";

const { bgcolors, palette, images } = ImageData;
const { bodies, accessories, heads, glasses } = images;

Get Noun Part & Background Data

import { getNounData } from "@noundry/nouns-assets";

const seed = {
  background: 0,
  body: 17,
  accessory: 41,
  head: 71,
  glasses: 2,
};
const { parts, background } = getNounData(seed);

Emulate NounSeeder.sol Pseudorandom seed generation

import { getNounSeedFromBlockHash } from "@noundry/nouns-assets";

const blockHash =
  "0x5014101691e81d79a2eba711e698118e1a90c9be7acb2f40d7f200134ee53e01";
const nounId = 116;

/**
 {
    background: 1,
    body: 28,
    accessory: 120,
    head: 95,
    glasses: 15
  }
*/
const seed = getNounSeedFromBlockHash(nounId, blockHash);

Examples

Almost off-chain Noun Crystal Ball Generate a Noun using only a block hash, which saves calls to NounSeeder and NounDescriptor contracts. This can be used for a faster crystal ball.

/**
 * For you to implement:
   - hook up providers with ether/web3.js
   - get currently auctioned Noun Id from the NounsAuctionHouse contract
   - add 1 to the current Noun Id to get the next Noun Id (named `nextNounId` below)
   - get the latest block hash from your provider (named `latestBlockHash` below)
*/

import {
  ImageData,
  getNounSeedFromBlockHash,
  getNounData,
} from "@noundry/nouns-assets";
import { buildSVG } from "@nouns/sdk";
const { palette } = ImageData; // Used with `buildSVG``

/**
 * OUTPUT:
   {
      background: 1,
      body: 28,
      accessory: 120,
      head: 95,
      glasses: 15
    }
*/
const seed = getNounSeedFromBlockHash(nextNounId, latestBlockHash);

/** 
 * OUTPUT:
   {
     parts: [
       {
         filename: 'body-teal',
         data: '...'
       },
       {
         filename: 'accessory-txt-noun-multicolor',
         data: '...'
       },
       {
         filename: 'head-goat',
         data: '...'
       },
       {
         filename: 'glasses-square-red',
         data: '...'
       }
     ],
     background: 'e1d7d5'
   }
*/
const { parts, background } = getNounData(seed);

const svgBinary = buildSVG(parts, palette, background);
const svgBase64 = btoa(svgBinary);

The Noun SVG can then be displayed. Here's a dummy example using React

function SVG({ svgBase64 }) {
  return <img src={`data:image/svg+xml;base64,${svgBase64}`} />;
}