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

fishsticks

v0.3.1

Published

Parse Node core compatible git info

Readme

fishsticks

Something about this request smells fishy.

Parse Node core compatible git info. Commit author information is extracted from the git commit Author field. Reviewer information is extracted from Reviewed-By: lines in the commit message.

Usage

Create a JavaScript file that exports a configuration object with the following properties:

  • repos (array) - An array of strings with each string representing the path to a locally cloned git repository.
  • emails (array) - An array of strings with each string representing an email address. Commit author and reviewer information is compared against the values in this array.
  • startDate (date) - Only report commits that occurred on, or after this date. This value is optional. If it is not included, the start date is assumed to be the beginning of time.
  • endDate (date) - Only report commits that occurred on, or before this date. This value is optional. If it is not included, the end date is assumed to be the end of time.

Next, run fishsticks -c path-to-config-file.js. The application will walk the git log of each repository. For each email address, the number of relevant authored and reviewed commits will be reported.

CLI Options

fishsticks supports the following command line options:

  • -c, --config (string) - The path to the configuration file.
  • -r, --report (string) - The format of the output. Optional. Supported formats are:
    • summary - Simple textual description of the number of commits. This is the default.
    • json - A JSON representation containing the full commit data.

Sample Config File

'use strict';
module.exports = {
  repos: [
    '/Users/peterpluck/node',
    '/Users/peterpluck/libuv'
  ],
  emails: [
    '[email protected]',
    '[email protected]'
  ],
  startDate: new Date('10-01-2016'),
  endDate: new Date('10-31-2016')
};