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

@ansemchain/ansem

v0.1.0

Published

ANSEMCHAIN chain explorer for your terminal. Ping the validators, watch blocks, check supply.

Readme

ansem

ANSEMCHAIN in your terminal.

npx @ansemchain/ansem

Launches a full-screen explorer. No commands to memorize:

  • ←/→ switch tabs (Overview · Validators · Blocks · Txs · Holders · Bridge · Supply)
  • ↑/↓ scroll
  • r refresh now (everything also auto-refreshes)
  • q quit

For scripts and CI there is a one-shot mode:

npx @ansemchain/ansem status          # human summary, exit 1 if the chain is unreachable
npx @ansemchain/ansem status --json   # machine-readable

Endpoints

| flag | env | default | | --- | --- | --- | | --rpc <url[,url…]> | ANSEM_RPC | http://195.72.61.234:26657 (testnet val1) | | --rest <url> | ANSEM_REST | http://195.72.61.234:1317 (testnet val1) | | --chain-id <id> | ANSEM_CHAIN_ID | ansem-1 |

Defaults point at the public ANSEM testnet, so npx @ansemchain/ansem works out of the box and keeps working across chain restarts/re-genesis (the endpoints are IP-pinned and every denom is read live from the chain). val2 is IPv6-only: http://[2a07:e043:1:19d::1]:26657 if you want a second endpoint on --rpc. For a localnet: ansem --rpc http://127.0.0.1:26657 --rest http://127.0.0.1:1317.

--rpc accepts a comma-separated list; every endpoint is pinged (latency + height) on the Validators tab, the first one is used for chain data. The tool verifies the reported chain id and warns if the endpoint serves a different chain (memechain's localnet uses the same ports).

Nothing is hardcoded about denoms: the native/gas token is read from the staking bond denom and bank denom metadata on the live chain.

  • Txs comes from CometBFT tx_search (actions + transfer amounts parsed from events, no proto decoding needed).
  • Holders is bank/denom_owners per denom (top holders + share bars).
  • Bridge reads the x/bridge REST routes (/bridge/v1/bridge_minted_supply, mint_records, burn_records) and falls back to voucher-denom bank supply for "total bridged" if the module isn't queryable.

If validator IPs ever change, update DEFAULT_RPC/DEFAULT_REST in bin/ansem.js, bump the version, and republish.

Dev

Zero runtime dependencies, Node >= 18.

node bin/ansem.js                 # run from the repo
node bin/ansem.js --rpc http://127.0.0.1:26657