@pnpm/render-peer-issues
Visualizes peer dependency issues
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@pnpm/error | AI (phantom-deps): @pnpm/error is declared in dependencies and is a same-org scoped package; phantom detection is a false positive for this pnpm monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): pnpm packages consistently publish without Sigstore provenance; this is a stable characteristic of the publisher's release pipeline. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1002.0.12 | 5 / 1 | |
| 1002.0.11 | 5 / 1 | |
| 1002.0.10 | 5 / 2 | |
| 1002.0.9 | 5 / 2 | |
| 1002.0.8 | 5 / 2 | |
| 1002.0.7 | 5 / 2 | |
| 1002.0.6 | 5 / 2 | |
| 1002.0.5 | 5 / 2 | |
| 1002.0.4 | 5 / 2 | |
| 1002.0.3 | 5 / 2 | |
| 1002.0.2 | 5 / 2 | |
| 1002.0.1 | 5 / 2 | |
| 1002.0.0 | 5 / 2 |
v1002.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1002.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1002.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.