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

terz-cli

v0.2.0

Published

Your package's adoption, on one page, on your own box.

Readme

terz

Your package's adoption, on one page, on your own box.

A run reads every registry your packages live on (npm, PyPI, Docker Hub, GitHub, GitLab), appends the readings to a plain file, and rewrites one static HTML page. No account, no database, nothing to keep running. The timer is yours.

npm install -g terz-cli

mkdir adoption && cd adoption
terz init          # writes terz.config.json
terz run           # takes a run, writes chart.html and terz.json

List your packages once, in terz.config.json:

{
  "name": "Acme",
  "products": [
    {
      "name": "Acme CLI",
      "slug": "acme-cli",
      "sources": { "npm": ["acme-cli"], "pypi": ["acme-cli"] }
    }
  ]
}

Then give the run to a timer. Once a day is right: the download APIs refresh daily, and reading them more often only spends rate limit.

0 8 * * *  cd /path/to/adoption && terz run

What a run leaves behind

  • chart.html · the chart, one self-contained file. Serve it, or open it off disk.
  • terz.json · the same chart as a document, for the Terz apps and anything else that wants the numbers. Schema: https://terz.dev.
  • readings.jsonl · every reading ever taken, one JSON object per line. Append-only; your history is a file you can read with tail and back up with cp.

A source that does not answer is held, not fatal: the chart keeps the last good value, dimmed, with a tag saying how long it has been held. A missing reading is never rendered as a zero; zero is a real measurement.

Revenue, optionally

Adoption and money on one page. Set a restricted, read-only Stripe key in the environment under STRIPE_KEY_<SLUG> and give the product its Stripe account id in the config ("stripe": "acct_…"). The next run lights up revenue, subscriptions and MRR. A secret key is refused territory: use a restricted key, which starts with rk_.

License

Proprietary, source-available. You may run it and read it; you may not redistribute it or rehost it as a service. Full terms in LICENSE.

Hosted, with sign-in and history kept for you: https://app.terz.dev · Docs and the product: https://terz.dev · Support: [email protected]