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 🙏

© 2024 – Pkg Stats / Ryan Hefner

hotspots

v0.0.3

Published

A tool that finds buggy spots in your codebase

Downloads

2

Readme

Hotspots

NPM

About

This tool uses Pivotal to identify which commits in your project are bug fixes, then analyzes those commits in your local git project to find which parts of your codebase need more attention. This is an implementation of the bug prediction solution a Google engineer posted. The difference being that instead of relying upon git commit messages, we can use other tools to provide identification of bug fix commits.

Dependencies

In order to analyze your codebase, your project must have been using:

  • a git repo
  • Pivotal Tracker
  • Pivotal Tracker Integration with Github

I am hoping to have more tool integration options other than Pivotal in the future.

Installation

$ npm install -g hotspots

The global is optional.

How to Use

You can use this tool as a command line utility or as a library

$ hotspots --help

The command line tool writes the file/score data to a csv file path of your choice, for easy visualization.

var findHotspots = require('hotspots');
findHotspots('<Pivotal API Token>', '<Project ID>', '<Project Path>', function(err, scoresByFile){
	// Do something great!
});

Contributing

I welcome all those who would like to help. All I ask is that you run your changes through the gulp eslint task before creating a pull request.