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

vanityssb

v1.0.9

Published

generate vanity keys for ssb

Readme

vanityssb

Crude discovery of vanity public keys that start with the specified text (case-insensitive). Four character vanity keys are easy to discover in less than a minute. Every additional character adds an exponential level of complexity.

Usage

npx vanityssb [string]

system load while running

Important:

After a key is found the result files must be deleted before another key search: rm -f done.txt key*

Usage: vanityssb <string> If no string is specified then $USER is used. The time to find a key grows exponentially with every character added to length of string. The program exits almost immediately when passed a single character. Within seconds when run as 'root' and takes multiple days when run with a 7 character string 'gardner'.

This design was the easiest to implement. No regard for optimization has been considered. Using the same npm lib as the system, we are guaranteed compatibility. After preliminary research into generating ed25519 by other means it was determined that verifying compatibility would be as complex as implementing this design. (X2)

Scaleway Paris C2M

tick[55]: avg[46981] ~ kps[47484] = secs[165] / tested[7840k]

Running on an Intel i7-4870HQ CPU @ 2.50GHz

tick[135]: avg[72055] ~ kps[69089] = secs[405] / tested[28010k]

Vultr Dallas Debian

tick[49]: avg[187844] ~ kps[189903] = secs[147] / tested[27970k]

Tests were conducted with node v6