@ledgerhq/errors
Advanced tools
Comparing version 5.0.0-alpha.3 to 5.0.0-alpha.4
{ | ||
"name": "@ledgerhq/errors", | ||
"version": "5.0.0-alpha.3+0b49d08", | ||
"version": "5.0.0-alpha.4+d82e4bd", | ||
"description": "Ledger common errors", | ||
@@ -31,3 +31,3 @@ "keywords": [ | ||
}, | ||
"gitHead": "0b49d08dedc19562fefbd2148292cc0995a0d4ae" | ||
"gitHead": "d82e4bd88e12b3d41c5dc6d7fb32944466b1cbcf" | ||
} |
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
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
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
1