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

mkkey

v0.4.2

Published

easy, breezy rsa keys

Readme

mkkey

mkkey makes ssh keys!

Installation

$ npm install -g mkkey

Usage

$ mkkey test

Output

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC5Ln8cFLFxZ+dNLXiBpyjTIiEVujZ5SGkVQnMj6d8USfY11zR3CqOP/AxQgX/kJs4Kb9y7EGOcdBvsXsxfW/z67IIPxn7881KNO1nbZYaUDP+5Ll6nM+ovpGh4LJb0/vYo+UHii8JGoiTZe1VGGgnyoEbjpDfSyDzPqtdE7rGKIf3/YYt98b0edljtYperBhvOVHtl2MwwU+0+Oq1l2vEvYLJ0h/zdBN/eQ9JP4IkzzhriabQOnrZE9lLMGoRwM3Rjl9TPVnhsoYnOeOTKVrlJoKXVmHkCDo9frhB4Oxn75q3h4x+jf1sfZ86MxyUhLK1z6/z7/Tc7Z+T0fqu5RAn7

What just happened?

  1. If ~/.ssh doesn't exist, it will be created
  2. test.pem private key was created
  3. The openssh-compatible public key was extracted from the private key and printed to stdout
  4. All permissions were properly set for the directory and the key

Namespaces

I like having a separate key for each user on each host, but putting all of those keys in ~/.ssh becomes unruly over time.

  • What if you have multiple keys to manage for a single host?
  • What if your usernames are used on multiple hosts?

Problem solved.

$ mkkey example.com/foo
...
$ mkkey example.com/bar
...

What just happened?

Everything is the same as above, except if a directory is specified, it will automatically be created for you.

  1. ~/ssh/example.com/foo.pem was created
  2. ~/ssh/example.com/bar.pem was created
  3. All permissions were properly set

Author

duchess [email protected]

License

BSD 3-clause