The differences between versions are fairly small and the code changes required to upgrade to the latest version tends to be straight-forward.

If you do require a version outside of this chart updated with patch fix, please contact me, otherwise I only plan to maintain the most recent major version.

If you identify a security vulnerability with this implementation, please do not hesitate to contact [email protected] immediately.

I try to respond within the same day and will address any concern as quickly as possible (including code fixes and publishing to NPM).

Any vulnerability will also be published to this file, along with credits, pertinent information and links to fixes.

The underlying scrypt algorithm has a known side-channel cache-timing attack, which cannot be addressed at the implementation level.

In many cases this is not a concern to most users and in a JavaScript context there are many other side-channel attacks to be concerned with, but here is an article which may be useful for those considering between scrypt and Argon2 (its main "competitor").