@pnpm/plugin-commands-rebuild
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/lockfile.types | AI (phantom-deps): Same-org @pnpm scope dep; declared in package.json as a direct dep, phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@pnpm/workspace.find-packages | AI (phantom-deps): Same-org @pnpm scope dep; consistent with pnpm monorepo structure, stable false positive. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1008.0.16 | 34 / 15 | |
| 1008.0.15 | 34 / 15 | |
| 1008.0.14 | 34 / 15 | |
| 1008.0.13 | 34 / 15 | |
| 1008.0.12 | 34 / 15 | |
| 1008.0.11 | 34 / 15 | |
| 1008.0.10 | 34 / 15 | |
| 1008.0.8 | 34 / 15 | |
| 1008.0.7 | 34 / 15 | |
| 1008.0.6 | 34 / 15 | |
| 1008.0.5 | 34 / 15 | |
| 1008.0.4 | 34 / 15 | |
| 1008.0.3 | 34 / 15 | |
| 1008.0.2 | 34 / 15 | |
| 1008.0.1 | 34 / 15 | |
| 1008.0.0 | 34 / 15 | |
| 1007.0.1 | 34 / 15 | |
| 1007.0.0 | 34 / 15 | |
| 1006.0.0 | 34 / 15 | |
| 1005.0.1 | 34 / 15 | |
| 1005.0.0 | 34 / 15 | |
| 1004.0.4 | 34 / 15 | |
| 1004.0.3 | 34 / 15 | |
| 1004.0.2 | 34 / 15 |
v1008.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1008.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1007.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1007.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1006.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1005.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1005.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1004.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1004.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1004.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.