crypto-js vs hash.js vs crypto vs jssha
JavaScript Cryptography Libraries
crypto-jshash.jscryptojsshaSimilar Packages:
JavaScript Cryptography Libraries

These libraries provide various cryptographic functionalities such as hashing, encryption, and decryption, which are essential for securing data in web applications. They cater to different needs, from built-in Node.js capabilities to lightweight browser-compatible solutions, enabling developers to implement security features effectively in their applications.

Npm Package Weekly Downloads Trend
3 Years
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
crypto-js6,136,77416,363487 kB2752 years agoMIT
hash.js6,044,424323-147 years agoMIT
crypto875,84532-148 years agoISC
jssha813,6062,265624 kB22 years agoBSD-3-Clause
Feature Comparison: crypto-js vs hash.js vs crypto vs jssha

Environment Compatibility

  • crypto-js:

    'crypto-js' is designed for use in both browser and Node.js environments. It allows developers to implement cryptographic functions in client-side applications, making it versatile for web development.

  • hash.js:

    'hash.js' is a standalone library that can be used in both Node.js and browser environments. It focuses on hashing algorithms, providing flexibility for developers needing hashing capabilities across different platforms.

  • crypto:

    The 'crypto' module is built into Node.js, making it only available in server-side applications. It provides a comprehensive set of cryptographic functionalities, including hashing, encryption, and digital signatures, but cannot be used in browser environments.

  • jssha:

    'jssha' is also compatible with both Node.js and browser environments. It is lightweight and straightforward, making it easy to integrate into various applications regardless of the platform.

Performance

  • crypto-js:

    'crypto-js' is designed to be lightweight and fast for client-side applications. However, performance may vary based on the complexity of the operations and the browser's capabilities.

  • hash.js:

    'hash.js' is optimized for speed, particularly for hashing operations. It is designed to handle large amounts of data efficiently, making it suitable for performance-critical applications that require fast hashing.

  • crypto:

    Being a native module, 'crypto' is optimized for performance in Node.js applications. It leverages the underlying system's cryptographic capabilities, ensuring efficient execution of cryptographic operations.

  • jssha:

    'jssha' is designed for quick hashing operations and is efficient in terms of performance. It provides a good balance between speed and usability, making it suitable for applications that require frequent hashing.

Supported Algorithms

  • crypto-js:

    'crypto-js' supports several popular algorithms, including MD5, SHA-1, SHA-256, and AES. It provides a good selection of algorithms for client-side encryption and hashing needs.

  • hash.js:

    'hash.js' specializes in hashing algorithms, supporting a variety of functions such as SHA-256, SHA-512, and more. It is focused on providing efficient hashing capabilities rather than encryption.

  • crypto:

    The 'crypto' module supports a wide range of cryptographic algorithms, including AES, RSA, SHA-256, and more. This extensive support makes it suitable for various cryptographic needs in server-side applications.

  • jssha:

    'jssha' offers a range of hashing algorithms, including SHA-1, SHA-256, and SHA-512. It is straightforward and easy to use for applications that require hashing without additional complexity.

Ease of Use

  • crypto-js:

    'crypto-js' is user-friendly and easy to integrate into applications. Its API is straightforward, making it accessible for developers with varying levels of experience.

  • hash.js:

    'hash.js' is designed to be simple and easy to use, focusing on hashing functionalities. It has a minimalistic API that allows developers to quickly implement hashing without extensive setup.

  • crypto:

    The 'crypto' module requires a deeper understanding of cryptographic concepts and Node.js APIs, which may present a learning curve for beginners. However, it offers powerful functionalities once mastered.

  • jssha:

    'jssha' is very easy to use, with a clear and concise API. It is ideal for developers looking for a straightforward solution for hashing without the need for complex configurations.

Community and Support

  • crypto-js:

    'crypto-js' has a strong community and is widely used in web development. It has good documentation and examples available, making it easy for developers to find support and resources.

  • hash.js:

    'hash.js' has a smaller community compared to others, but it is still actively maintained. Documentation is available, but developers may find fewer resources compared to more popular libraries.

  • crypto:

    As a built-in Node.js module, 'crypto' benefits from extensive documentation and community support through Node.js resources. It is well-maintained and regularly updated as part of the Node.js ecosystem.

  • jssha:

    'jssha' has a growing community and is easy to find support for, with clear documentation and examples. It is less widely used than some others but still offers sufficient resources for developers.

How to Choose: crypto-js vs hash.js vs crypto vs jssha
  • crypto-js:

    Choose 'crypto-js' for client-side applications where you need a lightweight library for hashing and encryption. It is easy to use and works well in browsers, making it suitable for applications that require cryptographic operations without relying on server-side capabilities.

  • hash.js:

    Select 'hash.js' if you need a library focused on hashing algorithms. It supports various hashing functions and is designed for performance, making it a good choice for applications that require fast and efficient hashing without additional overhead.

  • crypto:

    Use the built-in 'crypto' module if you are working in a Node.js environment and need access to a comprehensive set of cryptographic functions without additional dependencies. It's ideal for server-side applications where performance and security are critical.

  • jssha:

    Opt for 'jssha' when you need a simple, straightforward library for hashing in JavaScript. It provides a variety of hashing algorithms and is particularly useful for applications that require quick and easy integration of hashing functionalities.

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.