moakk/npmstats

Analysis updated 2026-06-24

★ 37TypeScriptAudience · developerComplexity · 2/5Setup · easy

Mindmap

mindmap
  root((npmstats))
    Inputs
      Package name
      Author name
      npm registry API
    Outputs
      Bar chart
      Line chart
      Author package list
    Use Cases
      Compare package popularity
      Track download trends
      Audit author output
    Tech Stack
      Next.js
      Tailwind
      shadcn
      Recharts

mindmap root((npmstats)) Inputs Package name Author name npm registry API Outputs Bar chart Line chart Author package list Use Cases Compare package popularity Track download trends Audit author output Tech Stack Next.js Tailwind shadcn Recharts

Click or tap to explore — scroll the page freely

What do people build with it?

USE CASE 1

Check download trends for an npm package before adding it as a dependency

USE CASE 2

List every package published by a specific npm author

USE CASE 3

Embed download charts in a docs site by forking the UI

What is it built with?

TypeScriptNext.jsTailwindshadcn/uiRecharts

How does it compare?

	moakk/npmstats	hotakus/opencode-visual-cache	javlonbek1233/greenroom
Stars	37	37	37
Language	TypeScript	TypeScript	TypeScript
Setup difficulty	easy	easy	easy
Complexity	2/5	2/5	1/5
Audience	developer	developer	vibe coder

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

In plain English

npmstats is a small web app that shows download numbers for any package on the npm registry. The README links to a hosted version at npmstats.dev, so you can use the site directly without cloning the project. You type a package name to look up its stats, or you look up an author to see every package they have published. The README lists four features. You can view download counts for daily, weekly, monthly, and yearly windows. The numbers can be drawn as a bar chart or a line chart. There is a dark mode and a light mode. And there is a per author page that lists every package belonging to one publisher. The stack is described in plain terms. The frontend is built with Next.js using its App Router. Styling is done with Tailwind CSS and shadcn/ui components. Charts are drawn with Recharts. The download numbers themselves come from the public npm registry download counts API, which the README links to. Running the project locally is two commands. You install dependencies with npm install, then start the dev server with npm run dev, and you open http://localhost:3000 in a browser. The README does not mention any environment variables, a database, or an auth step, which suggests the app reads directly from the public npm API at runtime. The README is short and does not list a license, a deployment guide, contribution rules, or tests. What you see in the README is everything the project documents about itself.

Copy-paste prompts

Prompt 1

Set up npmstats locally and point the dev server at a custom npm registry mirror

Prompt 2

Add a CSV export button to the npmstats package page that downloads the current chart data

Prompt 3

Replace Recharts with Chart.js in npmstats and keep the bar and line view toggle working

Prompt 4

Add a route to npmstats that compares two package names side by side on one chart

Frequently asked questions

What is npmstats?

Web app that shows daily, weekly, monthly, and yearly download stats for any npm package, with per-author pages listing all packages by one publisher.

What language is npmstats written in?

Mainly TypeScript. The stack also includes TypeScript, Next.js, Tailwind.

How hard is npmstats to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is npmstats for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.