web3-errors
Advanced tools
web3-errors - npm Package Compare versions
Comparing version 1.2.0 to 1.2.1-dev.1436228.0
| { | ||
| "name": "web3-errors", | ||
| "version": "1.2.0", | ||
| "version": "1.2.1-dev.1436228.0+1436228", | ||
| "description": "This package has web3 error classes", | ||
@@ -44,3 +44,3 @@ "main": "./lib/commonjs/index.js", | ||
| "dependencies": { | ||
| "web3-types": "^1.6.0" | ||
| "web3-types": "1.7.1-dev.1436228.0+1436228" | ||
| }, | ||
@@ -61,3 +61,3 @@ "devDependencies": { | ||
| }, | ||
| "gitHead": "506799287d70f866a5ff65df611a8be7161fae51" | ||
| "gitHead": "1436228817c7e6362e7a82b8f79ec3b2e9c99412" | ||
| } |
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
Manifest confusion
Supply chain riskThis package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.
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
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
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
Improved metrics
- Total package byte prevSize
- increased by0.01%
415704
Worsened metrics
- Number of low quality alerts
- increased by100%
2
Dependency changes
- Removedweb3-types@1.9.0(transitive)