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

eshistory

v0.0.4

Published

Library and utilities to extract code metrics from JS projects commit by commit.

Readme

ESHistory

Tool for extracting historical software metrics from JavaScript projects.

Installation

Use the following command to install eshistory:

sudo npm install -g eshistory

The sudo command must be used to install the package globally.

Usage

The basic usage is pretty simple, just call eshistory and pass two arguments: (a) the GIT repository containing the project, (b) the output file where metrics and metadata will be saved, e.g.

eshistory repository output.sql

Options

The command has some options to alter the default behavior, we recommend you to take a look in the command help (--help) to list the available options.

Verbose usage

The verbose option (-v) will get you detailed information (on stderr) about the metrics extraction process. We strongly reccomend the use of this flag.

Database structure

The output file is a SQL file to be used with a MySQL server. The database structure must be created prior to the data import.

We provided a SQL script in the path 'doc/database.sql' to created the necessary structure.