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

pwnd

v1.0.2

Published

A CLI that checks if your passwords have been compromised in a data breach

Readme

Description

A simple CLI tool that takes a list of passwords as shown below, queries the haveibeenpwned API and lets you know if they have been compromised in a data breach.

Why

Use a password that has yet to be leaked in a breach.

How

You provide one or more passwords which are hashed using SHA-1 (it's ok as the password isn't stored anywhere). Then using a system called k-anonymity, only the first five characters of your hashed password are used to query the pwned API which subsequently returns a set of hashed passwords that might match a given password.

The actually checking to see if a given password has been breached happens locally so your actual passwords are never sent anywhere (read more).

Install

npm install pwnd

You can also use npx if you're using npm version [email protected] and above

npx pwnd password1 reallylongpasswordoverhere other etc.

Usage

pwnd password1 reallylongpasswordoverhere other etc.

or

Create a pwnd-config.json file with a property called passwords that's mapped to an array of passwords like so:

{
  "passwords": ["password1", "reallylongpasswordoverhere", "other", "etc."]
}

Once you have created the pwnd-config.json file, simply run pwnd (with no arguments) in the same directory as the pwnd-config.json file like so:

pwnd

License

MIT © Evans Owino