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

github-bugspots

v1.1.3

Published

![node](https://img.shields.io/node/v/github-bugspots.svg) [![MIT License](http://img.shields.io/badge/license-MIT-blue.svg?style=flat)](LICENSE)

Downloads

21

Readme

github-bugspots

node MIT License

github-bugspots is based on bugspots which is an implementation of the simple bug prediction heuristic outlined by the Google Engineering team (Bug Predition at Google).
The difference is that github-bugspots is customised for GitHub, and github-bugspots's featues are as follows.

github-bugspots

  • works only on GitHub.
  • is same logic as bugspots. (However, the implementation method is difference, so result scores are just little difference.)
  • does not require to git clone the repositories before predictions.
  • internally works by using GitHub API.

Motivation

bugspots is very useful tool for getting the bug prediction.
However, to use bugspots, you must install it in local computer and git clone the target repository. Furthermore, it is not a library, so it is not easy to use in your program.

I want to use easily, for example, in web application.
Therefore, github-bugspots is made of Node.js. And github-bugspots has two interfaces, one is a cli, another is a library.

How to use for cli

$ npm install -g github-bugspots
$ github-bugspots --help
$ github-bugspots target_organization target_repository your_token

How to use for library

$ npm install --save github-bugspots
const Bugspots = require('github-bugspots');

new Bugspots(organization, repository, token).analyze(branch, regex)
  .then(function (data) {
    console.log(data)
  });

Notification

github-bugspots internally uses GitHub API.
So that, when you use github-bugspots for many repositories or repositories including many commits in a short time, you will be restricted for GitHub API rate limiting and occurs errors.
See details here.