brix / 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 module. The latest version of CryptoJS already uses the native Crypto module for random number generation, since 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 module. Node.js (Install) Requirements: • Node.js • npm (Node.js package manager) Usage ES6 import for typical API call signing use case: Modular include: Including all libraries, for access to extra methods: Client (browser) Requirements: • Node.js • Bower (package manager for frontend) Usage Modular include: Including all libraries, for access to extra methods: Usage without RequireJS API See: https://cryptojs.gitbook.io/docs/ AES Encryption Plain text encryption Object encryption List of modules • • • --- • • • • • • • • --- • • • • • • • • --- • --- • • • • • • --- • • --- • • • • • --- • • • • • --- • • • • • • 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 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, is the same as . The move of using native secure crypto module will be shifted to a new 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 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 version. Encrypting and decrypting stays compatible. But keep in mind versions still use which is cryptographically not secure, as it's not random enough. This version came along with . DO NOT USE THIS VERSION! Please, go for a newer version! 3.1.x The are based on the original CryptoJS, wrapped in CommonJS modules.