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

check-my-secrets

v0.0.3

Published

NodeJS script checking whether any of the passwords used online are compromised.

Downloads

6

Readme

Check My Secrets

NodeJS script checking whether any of the passwords used online are compromised.

It uses the ';--have i been pwned? V3 API, specifically the GET https://api.pwnedpasswords.com/range/{first 5 hash chars} to determine if a password is compromised.

Requirements

  • Node >= v17

Getting started

  1. Clone the repo :point_up:, for example:
git clone https://github.com/koalyptus/check-my-secrets.git
  1. Install all the requirements:
npm install
  1. Create a .env file at same location of this README with following definitions:
# Replace the curly brackets too!

# Encryption key used by Keyring
ENCRYPTION_KEY={your-encryption-key-here}

# Symbol used to separate passwords, defaults to `,`
PWDS_SEPARATOR={separator_here}

# Key used by Keyring to store the comma (or symbol of your choice) separated passwords
PWDS_KEY=checkmysecrets.{your-key-for-passwords}

:warning: If env file is not present the script will default to following values in same order of appearance in .env file:

hello-world-123
,
checkmysecrets.pwds

Please note that failing to provide a .env poses obvious security risks as the encryption key is publicly disclosed here.

  1. In command line use following command to set the comma (or any symbol of your choice) separated passwords in Keyring:
keyring store -k checkmysecrets.{PWDS_KEY HERE} -v 'my-password,another-password' -e -p {ENCRYPTION_KEY HERE}

:warning: the command even when executed successfully outputs some warnings related to deprecated dependencies. Disregard these for the time being.

To list the passwords use the following command:

keyring retrieve -k 'checkmysecrets.{PWDS_KEY HERE}' -d -p '{ENCRYPTION_KEY HERE}'
  1. Finally use npm start command to check the integrity of your passwords, alternatively node bin/check-my-secrets. Depending on the OS a notification similar to below should pop-out:

Check My Secrets notification