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

@revertwtf/catalog

v0.1.2

Published

Curated catalog of EVM, RPC, wallet, account abstraction, and protocol errors

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mrtdlgcmrtdlgc

Keywords

evmethereumcatalogsolidityrpcerc-4337x402

Readme

@revertwtf/catalog

Curated catalog of EVM, RPC, wallet, account abstraction, and protocol errors.

pnpm add @revertwtf/catalog
  • getCatalog() - all entries
  • getEntry(id) - single entry
  • searchCatalog(q) - string search across id/title/summary/category/source metadata
  • getEntriesByLayer(layer) / getEntriesByCategory(cat)
  • getCatalogSourceMetadata(source) - source display name, aliases, lifecycle, notes
  • getBlockscoutChains() / getBlockscoutChain(chainId) - generated Blockscout registry snapshot
  • searchBlockscoutChains(q) / getBlockscoutChainStats() - Blockscout chain lookup helpers
  • describePanic("0x11") - Solidity panic-code dictionary, also available as the tiny @revertwtf/catalog/panic subpath
  • normalizePanicCode("0x000...0011") - canonicalizes valid 0x-prefixed panic-code hex and rejects ambiguous values such as "17"

Entries are pure data in src/data/shards/. Source display names and lifecycle labels live in src/sources.ts so raw source IDs stay stable.

@revertwtf/catalog is the full catalog surface. Browser apps that only need small dictionaries or one shard should use explicit subpaths so they do not bundle the full catalog data by accident.

Bundle-size guide

| Subpath | Approx size | Use when | | --- | ---: | --- | | @revertwtf/catalog/panic | < 2 KB | only need Solidity panic codes | | @revertwtf/catalog/shards + loadShard("solidity") | ~10 KB for solidity, varies by shard | client or server app needs one shard | | @revertwtf/catalog/data-full | very large raw JSON | server-side, need everything | | @revertwtf/catalog | full catalog surface | server-side programmatic catalog access |

Blockscout chain coverage lives in src/data/blockscout-chains.json, generated from Blockscout. Refresh it with pnpm catalog:update-blockscout, then run pnpm catalog:build-data, pnpm validate:catalog, and pnpm catalog:duplicates.