@pnpm/lockfile-types
Types for the pnpm-lock.yaml lockfile
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.1.3 | 1 / 1 | |
| 7.1.2 | 1 / 1 | |
| 7.1.1 | 1 / 1 | |
| 7.1.0 | 1 / 1 | |
| 7.0.0 | 1 / 1 | |
| 5.1.5 | 1 / 1 |
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pnpmuser) than the most recent previously approved version (zkochan) on 2024-06-10, but pnpmuser is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v7.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zkochan) than the most recent previously approved version (pnpmuser) on 2024-05-21, but zkochan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.