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

bcrypt-speed

v0.0.9

Published

Determine how many rounds can be used for a given maximum amount of login time

Readme

bcrypt-speed

Determine the maximum level of rounds for some hardware given the maximum time that can be spent on login.

Using a fixed amount of time (and thus having an assured user experience) this module runs a couple of different bcrypt implementations so that the optimum number of rounds can be found given some hardware and the time that a login may take (i.e. Apple uses 80ms for unlocking).

Note: this package should be run on the target production hardware to get a good estimate.

The following packages are currently tested:

Any suggestions on other bcrypt implementations are welcome.

Remember, even MD4 would be sufficient when using a strong password, so consider using a Diceware passphrase.

Usage

$ node bcrypt-speed.js [maxtime]

A maxtime is optional and defaults to 100ms. This should be the maximum time you want to let your users wait while you're verifying their password.

Example

Example run on a 3 GHz core:

$ node bcrypt-speed.js
test duration per number of rounds, up to 100ms

bcrypt-nodejs (pure js, no deps)
rounds  ms
  4      8
  5      9
  6     15
  7     31
  8     53
  9    108

twin-bcrypt (pure js, no deps, asm.js)
rounds  ms
  4      8
  5      7
  6     12
  7     26
  8     48
  9     92
 10    184

bcryptjs (pure js, no deps)
rounds  ms
  4      9
  5      8
  6     16
  7     32
  8     57
  9    114

bcrypt (c++, has deps)
rounds  ms
  4      1
  5      3
  6      5
  7      9
  8     18
  9     38
 10     76
 11    150

Further reading

Discussion about bcrypt, password cracking speed and Diceware passphrases:

License

ISC

Copyright (c) 2014, 2015 Tim Kuijsten

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.