near-seed-phrase
Advanced tools
near-seed-phrase - npm Package Compare versions
Comparing version 0.2.0 to 0.2.1
| { | ||
| "name": "near-seed-phrase", | ||
| "version": "0.2.0", | ||
| "version": "0.2.1", | ||
| "description": "Utilities to work with NEAR Protocol key pairs based on seed phrases ", | ||
@@ -8,4 +8,10 @@ "main": "index.js", | ||
| "scripts": { | ||
| "test": "mocha" | ||
| "test": "mocha", | ||
| "dist": "browserify browser-exports.js -i node-fetch -i http -i https -o dist/near-seed-phrase.js && browserify browser-exports.js -i node-fetch -g uglifyify -o dist/near-seed-phrase.min.js" | ||
| }, | ||
| "types": "types.d.ts", | ||
| "files": [ | ||
| "dist/", | ||
| "types.d.ts" | ||
| ], | ||
| "dependencies": { | ||
@@ -18,4 +24,6 @@ "bip39-light": "^1.0.7", | ||
| "devDependencies": { | ||
| "mocha": "^8.1.3" | ||
| "browserify": "^17.0.0", | ||
| "mocha": "^8.1.3", | ||
| "uglifyify": "^5.0.2" | ||
| } | ||
| } |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
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
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
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
Minified code
QualityThis package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No README
QualityPackage does not have a README. This may indicate a failed publish or a low quality package.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by34421.66%
1566938
- Lines of code
- increased by48771.83%
34699
- Number of medium quality alerts
- decreased by-100%
0
- Number of lines in readme file
- increased byInfinity%
20
Worsened metrics
- Dev dependency count
- increased by200%
3
- Number of low quality alerts
- increased by50%
3
- Number of low supply chain risk alerts
- increased by1200%
13
- Number of medium supply chain risk alerts
- increased byInfinity%
4