@pnpm/lockfile.utils
Advanced tools
Comparing version 1.0.2 to 1.0.3
{ | ||
"name": "@pnpm/lockfile.utils", | ||
"version": "1.0.2", | ||
"version": "1.0.3", | ||
"description": "Utils for dealing with pnpm-lock.yaml", | ||
@@ -31,3 +31,3 @@ "main": "lib/index.js", | ||
"yaml-tag": "1.1.0", | ||
"@pnpm/lockfile.utils": "1.0.2" | ||
"@pnpm/lockfile.utils": "1.0.3" | ||
}, | ||
@@ -37,7 +37,7 @@ "dependencies": { | ||
"ramda": "npm:@pnpm/ramda@0.28.1", | ||
"@pnpm/dependency-path": "5.1.5", | ||
"@pnpm/dependency-path": "5.1.6", | ||
"@pnpm/lockfile.types": "1.0.3", | ||
"@pnpm/pick-fetcher": "3.0.0", | ||
"@pnpm/resolver-base": "13.0.3", | ||
"@pnpm/lockfile.types": "1.0.2", | ||
"@pnpm/types": "12.1.0" | ||
"@pnpm/resolver-base": "13.0.4", | ||
"@pnpm/types": "12.2.0" | ||
}, | ||
@@ -44,0 +44,0 @@ "funding": "https://opencollective.com/pnpm", |
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
0
+ Added@pnpm/dependency-path@5.1.6(transitive)
+ Added@pnpm/lockfile.types@1.0.3(transitive)
+ Added@pnpm/resolver-base@13.0.4(transitive)
+ Added@pnpm/types@12.2.0(transitive)
- Removed@pnpm/dependency-path@5.1.5(transitive)
- Removed@pnpm/lockfile.types@1.0.2(transitive)
- Removed@pnpm/resolver-base@13.0.3(transitive)
- Removed@pnpm/types@12.1.0(transitive)
Updated@pnpm/dependency-path@5.1.6
Updated@pnpm/lockfile.types@1.0.3
Updated@pnpm/resolver-base@13.0.4
Updated@pnpm/types@12.2.0