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

hubot-guys

v0.0.1

Published

Listens for mentions of 'guys' and responds with helpful alternatives

Readme

hubot-guys

Listens for mentions of 'guys' and responds with helpful alternatives. The original idea came from Adrienne Marshall.

Installation

In hubot project repo, run:

npm install hubot-guys --save

Then add hubot-guys to your external-scripts.json:

["hubot-guys"]

Sample Interaction

user1>> What's up guys?
hubot>> Why not try 'buds' instead?

Why would you do something like this?

Because language is an important part of the way we communicate our culture and can affect those around us. By addressing people with a gender-specific word you can subtly exclude those who don't self-identify as 'guys'.

Getting Hubot (or the original Slackbot) to gently remind people they're using language that can exclude, struck me as a nice way to encourage people to be more inclusive.

If you want a longer explanation, Jenée Desmond-Harris wrote an article on this on Vox