@pnpm/lockfile-file
Read/write pnpm-lock.yaml files
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
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 |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 9.1.3 | 19 / 9 | |
| 9.1.2 | 19 / 9 | |
| 9.1.1 | 19 / 9 | |
| 9.1.0 | 19 / 9 | |
| 9.0.6 | 19 / 9 | |
| 9.0.5 | 19 / 9 | |
| 9.0.4 | 19 / 9 | |
| 9.0.3 | 19 / 9 | |
| 9.0.2 | 19 / 9 | |
| 9.0.1 | 18 / 9 | |
| 9.0.0 | 18 / 9 | |
| 8.1.8 | 17 / 9 |
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
2 findings[Accepted risk] Package 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-17, 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.
v9.1.0
2 findings[Accepted risk] Package 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.
v9.0.6
2 findings[Accepted risk] Package 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.
v9.0.5
2 findings[Accepted risk] Package 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-12, 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.
v9.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
2 findings[Accepted risk] Package 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-04-21, 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.
v9.0.0
2 findings[Accepted risk] Package 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-04-09, 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.