@originjs/crypto-js-wasm
Advanced tools
Comparing version 1.0.0 to 1.1.0-beta0
{ | ||
"name": "@originjs/crypto-js-wasm", | ||
"version": "1.0.0", | ||
"description": "An alternate to crypto-js implemented with WebAssembly and ESM", | ||
"version": "1.1.0-beta0", | ||
"description": "An alternative to crypto-js implemented with WebAssembly and ESM", | ||
"main": "lib/index.js", | ||
"files": ["lib"], | ||
"files": [ | ||
"lib" | ||
], | ||
"scripts": { | ||
@@ -62,2 +64,3 @@ "build": "npm run clean && node build/build.js", | ||
"@babel/core": "^7.6.3", | ||
"@babel/eslint-parser": "^7.18.9", | ||
"@babel/plugin-proposal-class-properties": "^7.16.7", | ||
@@ -67,7 +70,7 @@ "@babel/plugin-transform-modules-commonjs": "^7.6.0", | ||
"@rollup/plugin-babel": "^5.3.1", | ||
"babel-eslint": "^10.0.3", | ||
"@rollup/plugin-commonjs": "^22.0.2", | ||
"babel-jest": "^24.9.0", | ||
"chalk": "^2.4.2", | ||
"crypto-js": "^4.1.1", | ||
"eslint": "^6.5.1", | ||
"eslint": "^8.21.0", | ||
"husky": "^3.0.8", | ||
@@ -79,3 +82,3 @@ "jest": "^27.5.1", | ||
"rimraf": "^3.0.0", | ||
"rollup": "1.22.0", | ||
"rollup": "^2.77.2", | ||
"terser": "^4.3.8", | ||
@@ -82,0 +85,0 @@ "zlib": "^1.0.5" |
@@ -18,2 +18,8 @@ # @originjs/crypto-js-wasm | ||
## What's new | ||
RSA is supported now! | ||
## Getting started | ||
@@ -67,2 +73,8 @@ | ||
**Usage of RSA** | ||
Please refer to [this document](./docs/rsa.md). | ||
**Available standards** | ||
@@ -91,7 +103,2 @@ | ||
- RC4Drop | ||
**Coming next** | ||
- RSA | ||
@@ -143,3 +150,3 @@ | ||
#### Why do we need a async loadWasm call? | ||
#### Why do we need an async loadWasm call? | ||
@@ -146,0 +153,0 @@ This is because the WebAssembly binary needs to be load by `WebAssembly.instantiate`, and it is async. |
Sorry, the diff of this file is too big to display
Uses eval
Supply chain riskPackage uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Found 1 instance in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
642624
7620
164
20
2
14
1