@pnpm/lockfile-utils 1.0.9

Utils for dealing with pnpm-lock.yaml

@pnpm/lockfile-utils@1.0.9 was published on 2019-06-02. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.15.

All @pnpm/lockfile-utils versions · Permanent reference to 1.0.9 · Latest release

Package specifications

Version	1.0.9
License declaration	MIT
Published	2019-06-02T17:56:01.683Z
Node.js requirement	>=8.15
Type declarations	Bundled declarations
Runtime dependency count	6
Peer requirement count	0
Optional dependency count	0
Minified size	Measurement not available yet
Minified + gzip	Measurement not available yet
Unpacked distribution size	9.56 KiB
Published file count	15
Package type	Not declared
ES module entry	Not declared
Default entry	lib/index.js
Side effects declaration	Not declared
Direct advisories	0
Resolved graph dependencies	14
Repository stars	36888
Repository forks	1957

Install @pnpm/lockfile-utils 1.0.9

npm install @pnpm/lockfile-utils@1.0.9
pnpm add @pnpm/lockfile-utils@1.0.9
yarn add @pnpm/lockfile-utils@1.0.9

Runtime dependencies

Peer requirements

None declared

Optional dependencies

None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

@pnpm/lockfile-types@1.1.0 — direct
@pnpm/resolver-base@3.1.2 — direct
@pnpm/types@3.2.0 — direct
dependency-path@3.0.7 — direct
encode-registry@2.0.0 — indirect
get-npm-tarball-url@2.0.1 — direct
map-age-cleaner@0.1.3 — indirect
mem@5.1.1 — indirect
mimic-fn@2.1.0 — indirect
normalize-registry-url@1.0.0 — indirect
p-defer@1.0.0 — indirect
p-is-promise@2.1.0 — indirect
ramda@0.26.1 — direct
semver@6.1.1 — indirect

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review	9/10 — Found 27/30 approved changesets -- score normalized to 9
Maintained	10/10 — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
Security-Policy	10/10 — security policy file detected
CII-Best-Practices	0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow	10/10 — no dangerous workflow patterns detected
Token-Permissions	0/10 — detected GitHub workflow tokens with excessive permissions
License	10/10 — license file detected
Binary-Artifacts	10/10 — no binaries found in the repo
Branch-Protection	5/10 — branch protection is not maximal on development and all release branches
Pinned-Dependencies	9/10 — dependency not pinned by hash detected -- score normalized to 9
Signed-Releases	0/10 — Project has not signed or included provenance with any releases.
Packaging	10/10 — packaging workflow detected
Fuzzing	0/10 — project is not fuzzed
SAST	10/10 — SAST tool is run on all commits

Evidence and freshness

https://registry.npmjs.org/%40pnpm%2Flockfile-utils/1.0.9 — retrieved 2026-10-29T21:47:47.999Z
https://api.deps.dev/v3/projects/github.com%2Fpnpm%2Fpnpm — retrieved 2026-10-29T19:09:44.976Z
https://api.deps.dev/v3/systems/npm/packages/%40pnpm%2Flockfile-utils/versions/1.0.9 — retrieved 2026-10-29T21:47:48.613Z
https://api.deps.dev/v3/systems/npm/packages/%40pnpm%2Flockfile-utils/versions/1.0.9:dependencies — retrieved 2026-10-29T21:47:48.637Z