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

@evergonlabs/tmi-protocol-indexer

v0.11.2

Published

This EVM-networks indexer is built on top of [ponder.sh](https://github.com/ponder-sh/ponder)

Downloads

1,118

Readme

Overview

This EVM-networks indexer is built on top of ponder.sh

Scripts

  • start — run indexer for production
  • start:dev — run indexer for dev environment

Networks mode

The network selection is determined by the networks mode:

  • dev — anvil
  • prod — sepolia (mainnet will be added soon)

Production

Database

In production you must specify which database schema it should use. This can be done through:

  • as DATABASE_SCHEMA env variable
  • as --schema CLI option with the start script

To pass the postgres URI you should use env variables:

  • POSTGRES_URI — connection uri to postgres instance

RPC nodes

Indexer requires RPC node of a network you will need to index. To provide it you should pass following env variables per network:

  • SEPOLIA_RPC — Sepolia