@pnpm/lockfile-file MIT 2 versions

@pnpm/lockfile-file

npm Repository Homepage

Read/write pnpm-lock.yaml files

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pnpmuserzkochan

Keywords

pnpm9pnpmshrinkwraplockfile

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established pnpm monorepo package; provenance not historically provided across its 119 versions.	ai	2026/04/29

Versions (showing 2 of 2)

Version	Deps	Published
9.1.3	19 / 9	2024-07-21
8.1.8	17 / 9	2024-02-24

v9.1.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.