npm-ui integrates download counts and other metadata (soon) with the NPM registry.

Sometimes the rich get richer because they should, and knowing who's who will save you time.

• npm-history. github. npm. Caching layer on top of npm, Inc.'s download-counts API, since the download counts data are not available en masse.
  • HTTP API
  • Requires PostgreSQL server available at localhost:5432
• npm-downloads-data. github. Populated with aggregates of data collected by npm-history.
  • Can use GitHub Pages
    • E.g., https://chbrown.github.io/npm-downloads-data/2015/04/averages.json
• npm-search-server. github. npm. Docker Hub.
  • HTTP API
  • Requires ElasticSearch server, Dockerized
  • Needs plenty of memory (at least, ES does)
  • Primed by pulling data from npm-downloads-data
• npm-ui. User interface for consuming the search-server API.
  • Served as gh-pages at chbrown.github.io/npm-ui/

Copyright 2014–2015 Christopher Brown. MIT Licensed.