@lerna/has-npm-version
Advanced tools
Comparing version 5.0.0-alpha.0 to 5.0.0-alpha.1
{ | ||
"name": "@lerna/has-npm-version", | ||
"version": "5.0.0-alpha.0", | ||
"version": "5.0.0-alpha.1", | ||
"description": "Test if the current version of npm satisfies a given semver range", | ||
@@ -31,6 +31,6 @@ "keywords": [ | ||
"dependencies": { | ||
"@lerna/child-process": "5.0.0-alpha.0", | ||
"@lerna/child-process": "5.0.0-alpha.1", | ||
"semver": "^7.3.4" | ||
}, | ||
"gitHead": "5451a79392742a6e942a845de1e46db0a41b1c2e" | ||
"gitHead": "66c961d55050634bb011e98c43aad5b2ec8505f9" | ||
} |
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
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
6253
5
0
+ Added@lerna/child-process@5.0.0-alpha.1(transitive)
- Removed@lerna/child-process@5.0.0-alpha.0(transitive)