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 🙏

© 2025 – Pkg Stats / Ryan Hefner

node-botometer

v0.1.7

Published

Evaluates Twitter accounts to determine whether they're bots

Readme

node-botometer

node-botometer evaluates Twitter accounts using Botometer, a project by the Indiana University Network Science Institute, that "checks the activity of a Twitter account and gives it a score based on how likely the account is to be a bot. Higher scores are more bot-like."

It uses Twit and Botometer's mashape API. Twitter application and Botometer mashape API keys are required.

Install

npm install node-botometer

Use

Setup

Use app-only keys consumer_key (string) and consumer_secret (string), and set app_only_auth (boolean) to true for less restrictive rate limiting from Twitter. User-level tokens access_token (string) and access_token_secret (string) are allowed but not required or recommended.

mashape_key (string): Get a key from Botometer's mashape API

rate_limit (integer): In milliseconds. Will apply to any calls to the Twitter or mashape APIs. Default: 0.

log_progress (boolean): Set to true to console log progress on score collection for each name. Default: true.

include_user (boolean): Include user data from Twitter in output object. Default: true.

include_timeline (boolean): Include the 200 most recent tweets from this user in output object. Default: false.

include_mentions (boolean): Include the 100 most recent mentions of this user in output object. Default: false.

const botometer = require('node-botometer');

const B = new botometer({
  consumer_key: '',
  consumer_secret: '',
  access_token: null,
  access_token_secret: null,
  app_only_auth: true,
  mashape_key: '',
  rate_limit: 0,
  log_progress: true,
  include_user: true,
  include_timeline: false,
  include_mentions: false
});

Get Botometer scores

You can get scores for one account or for many. It takes about six seconds per account and I'm looking for ideas to make it faster!

// array can be one screen name or many
const names = ["collinskeith","usinjuries","actual_ransom"];

B.getBatchBotScores(names,data => {
  console.log(data);
});