crypto-js vs crypto-browserify
JavaScript Cryptography Libraries Comparison
3 Years
crypto-jscrypto-browserifySimilar Packages:
What's JavaScript Cryptography Libraries?

JavaScript cryptography libraries provide essential tools for implementing cryptographic algorithms and protocols in web applications. They enable developers to secure data through encryption, hashing, and other cryptographic techniques, ensuring data integrity and confidentiality. These libraries are crucial for building secure applications, especially in environments where sensitive data is handled, such as user authentication, secure communications, and data storage.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
crypto-js9,084,544
16,291487 kB2752 years agoMIT
crypto-browserify8,502,294
68256 kB38a year agoMIT
Feature Comparison: crypto-js vs crypto-browserify

Algorithm Support

  • crypto-js:

    crypto-js offers a rich set of cryptographic algorithms, including AES, DES, Triple DES, MD5, SHA-1, SHA-256, and HMAC. It is designed to be straightforward and efficient, providing a simple API for developers to implement encryption and hashing in their applications.

  • crypto-browserify:

    crypto-browserify supports a wide range of cryptographic algorithms, including AES, SHA-1, SHA-256, HMAC, and more. It aims to provide a consistent API that mirrors Node.js's crypto module, making it easier for developers familiar with Node.js to transition to browser-based applications.

Performance

  • crypto-js:

    crypto-js is designed to be lightweight and fast, making it suitable for performance-sensitive applications. It is particularly efficient for hashing operations and symmetric encryption, allowing developers to implement cryptographic functions without significant overhead.

  • crypto-browserify:

    crypto-browserify is optimized for performance in the browser, but its performance may vary depending on the specific algorithms used and the complexity of the operations. It is generally efficient for most use cases, although developers should be mindful of the performance implications of using certain algorithms in resource-constrained environments.

Ease of Use

  • crypto-js:

    crypto-js is known for its simplicity and ease of use, with a straightforward API that allows developers to quickly implement cryptographic functions. Its clear documentation and examples make it accessible for developers of all skill levels.

  • crypto-browserify:

    crypto-browserify provides a familiar API for developers who have experience with Node.js, making it easier to integrate cryptographic functions into web applications. However, some users may find the need for polyfills or additional configuration when using it in certain environments.

Compatibility

  • crypto-js:

    crypto-js is a standalone library that does not rely on Node.js, making it suitable for use in any JavaScript environment, including browsers and mobile applications. Its independence from Node.js allows for greater flexibility in deployment.

  • crypto-browserify:

    crypto-browserify is designed to be compatible with existing Node.js code, allowing developers to reuse their server-side cryptographic logic in browser applications. This compatibility makes it an excellent choice for full-stack JavaScript applications that require consistent cryptographic functionality across environments.

Security Considerations

  • crypto-js:

    crypto-js provides a range of cryptographic functions, but developers should be cautious about using outdated algorithms or weak configurations. It is important to stay informed about best practices in cryptography and to use strong keys and secure modes of operation.

  • crypto-browserify:

    crypto-browserify aims to provide secure implementations of cryptographic algorithms, but developers must remain vigilant about potential vulnerabilities and ensure they are using up-to-date versions of the library. Proper implementation and understanding of cryptographic principles are essential for maintaining security.

How to Choose: crypto-js vs crypto-browserify
  • crypto-js:

    Choose crypto-js if you are looking for a lightweight library focused on providing a variety of cryptographic algorithms, such as AES, SHA, and HMAC. It is ideal for projects that require simple and efficient encryption and hashing without the need for extensive Node.js compatibility.

  • crypto-browserify:

    Choose crypto-browserify if you need a comprehensive solution that mimics Node.js's built-in crypto module for use in the browser. It is particularly useful for applications that require compatibility with existing Node.js code and a wide range of cryptographic functions, including hashing and HMACs.

README for crypto-js

crypto-js

JavaScript library of crypto standards.

Discontinued

Active development of CryptoJS has been discontinued. This library is no longer maintained.

Nowadays, NodeJS and modern browsers have a native Crypto module. The latest version of CryptoJS already uses the native Crypto module for random number generation, since Math.random() is not crypto-safe. Further development of CryptoJS would result in it only being a wrapper of native Crypto. Therefore, development and maintenance has been discontinued, it is time to go for the native crypto module.

Node.js (Install)

Requirements:

  • Node.js
  • npm (Node.js package manager)
npm install crypto-js

Usage

ES6 import for typical API call signing use case:

import sha256 from 'crypto-js/sha256';
import hmacSHA512 from 'crypto-js/hmac-sha512';
import Base64 from 'crypto-js/enc-base64';

const message, nonce, path, privateKey; // ...
const hashDigest = sha256(nonce + message);
const hmacDigest = Base64.stringify(hmacSHA512(path + hashDigest, privateKey));

Modular include:

var AES = require("crypto-js/aes");
var SHA256 = require("crypto-js/sha256");
...
console.log(SHA256("Message"));

Including all libraries, for access to extra methods:

var CryptoJS = require("crypto-js");
console.log(CryptoJS.HmacSHA1("Message", "Key"));

Client (browser)

Requirements:

  • Node.js
  • Bower (package manager for frontend)
bower install crypto-js

Usage

Modular include:

require.config({
    packages: [
        {
            name: 'crypto-js',
            location: 'path-to/bower_components/crypto-js',
            main: 'index'
        }
    ]
});

require(["crypto-js/aes", "crypto-js/sha256"], function (AES, SHA256) {
    console.log(SHA256("Message"));
});

Including all libraries, for access to extra methods:

// Above-mentioned will work or use this simple form
require.config({
    paths: {
        'crypto-js': 'path-to/bower_components/crypto-js/crypto-js'
    }
});

require(["crypto-js"], function (CryptoJS) {
    console.log(CryptoJS.HmacSHA1("Message", "Key"));
});

Usage without RequireJS

<script type="text/javascript" src="path-to/bower_components/crypto-js/crypto-js.js"></script>
<script type="text/javascript">
    var encrypted = CryptoJS.AES(...);
    var encrypted = CryptoJS.SHA256(...);
</script>

API

See: https://cryptojs.gitbook.io/docs/

AES Encryption

Plain text encryption

var CryptoJS = require("crypto-js");

// Encrypt
var ciphertext = CryptoJS.AES.encrypt('my message', 'secret key 123').toString();

// Decrypt
var bytes  = CryptoJS.AES.decrypt(ciphertext, 'secret key 123');
var originalText = bytes.toString(CryptoJS.enc.Utf8);

console.log(originalText); // 'my message'

Object encryption

var CryptoJS = require("crypto-js");

var data = [{id: 1}, {id: 2}]

// Encrypt
var ciphertext = CryptoJS.AES.encrypt(JSON.stringify(data), 'secret key 123').toString();

// Decrypt
var bytes  = CryptoJS.AES.decrypt(ciphertext, 'secret key 123');
var decryptedData = JSON.parse(bytes.toString(CryptoJS.enc.Utf8));

console.log(decryptedData); // [{id: 1}, {id: 2}]

List of modules

  • crypto-js/core
  • crypto-js/x64-core
  • crypto-js/lib-typedarrays

  • crypto-js/md5
  • crypto-js/sha1
  • crypto-js/sha256
  • crypto-js/sha224
  • crypto-js/sha512
  • crypto-js/sha384
  • crypto-js/sha3
  • crypto-js/ripemd160

  • crypto-js/hmac-md5
  • crypto-js/hmac-sha1
  • crypto-js/hmac-sha256
  • crypto-js/hmac-sha224
  • crypto-js/hmac-sha512
  • crypto-js/hmac-sha384
  • crypto-js/hmac-sha3
  • crypto-js/hmac-ripemd160

  • crypto-js/pbkdf2

  • crypto-js/aes
  • crypto-js/tripledes
  • crypto-js/rc4
  • crypto-js/rabbit
  • crypto-js/rabbit-legacy
  • crypto-js/evpkdf

  • crypto-js/format-openssl
  • crypto-js/format-hex

  • crypto-js/enc-latin1
  • crypto-js/enc-utf8
  • crypto-js/enc-hex
  • crypto-js/enc-utf16
  • crypto-js/enc-base64

  • crypto-js/mode-cfb
  • crypto-js/mode-ctr
  • crypto-js/mode-ctr-gladman
  • crypto-js/mode-ofb
  • crypto-js/mode-ecb

  • crypto-js/pad-pkcs7
  • crypto-js/pad-ansix923
  • crypto-js/pad-iso10126
  • crypto-js/pad-iso97971
  • crypto-js/pad-zeropadding
  • crypto-js/pad-nopadding

Release notes

4.2.0

Change default hash algorithm and iteration's for PBKDF2 to prevent weak security by using the default configuration.

Custom KDF Hasher

Blowfish support

4.1.1

Fix module order in bundled release.

Include the browser field in the released package.json.

4.1.0

Added url safe variant of base64 encoding. 357

Avoid webpack to add crypto-browser package. 364

4.0.0

This is an update including breaking changes for some environments.

In this version Math.random() has been replaced by the random methods of the native crypto module.

For this reason CryptoJS might not run in some JavaScript environments without native crypto module. Such as IE 10 or before or React Native.

3.3.0

Rollback, 3.3.0 is the same as 3.1.9-1.

The move of using native secure crypto module will be shifted to a new 4.x.x version. As it is a breaking change the impact is too big for a minor release.

3.2.1

The usage of the native crypto module has been fixed. The import and access of the native crypto module has been improved.

3.2.0

In this version Math.random() has been replaced by the random methods of the native crypto module.

For this reason CryptoJS might does not run in some JavaScript environments without native crypto module. Such as IE 10 or before.

If it's absolute required to run CryptoJS in such an environment, stay with 3.1.x version. Encrypting and decrypting stays compatible. But keep in mind 3.1.x versions still use Math.random() which is cryptographically not secure, as it's not random enough.

This version came along with CRITICAL BUG.

DO NOT USE THIS VERSION! Please, go for a newer version!

3.1.x

The 3.1.x are based on the original CryptoJS, wrapped in CommonJS modules.