@pnpm/plugin-commands-publishing
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:execa | AI (phantom-deps): execa is aliased to safe-execa in dependencies; phantom-dep heuristic misfires on npm aliases. | ai | |
| phantom-deps | phantom-dep:@pnpm/resolver-base | AI (phantom-deps): Same-org @pnpm scoped package; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@pnpm/catalogs.types | AI (phantom-deps): Same-org @pnpm scoped package; stable false positive for this monorepo package. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 1000.3.22 | 32 / 23 | |
| 1000.3.21 | 32 / 23 | |
| 1000.3.20 | 32 / 23 | |
| 1000.3.19 | 32 / 23 | |
| 1000.3.18 | 32 / 23 | |
| 1000.3.17 | 32 / 23 | |
| 1000.3.16 | 32 / 23 | |
| 1000.3.15 | 32 / 23 | |
| 1000.3.14 | 32 / 23 | |
| 1000.3.13 | 32 / 23 | |
| 1000.3.12 | 32 / 23 | |
| 1000.3.10 | 32 / 23 | |
| 1000.3.9 | 32 / 23 | |
| 1000.3.8 | 32 / 23 | |
| 1000.3.7 | 32 / 23 | |
| 1000.3.6 | 32 / 23 | |
| 1000.3.5 | 32 / 23 | |
| 1000.3.4 | 32 / 23 | |
| 1000.3.3 | 32 / 22 | |
| 1000.3.2 | 32 / 22 | |
| 1000.3.1 | 32 / 22 | |
| 1000.3.0 | 32 / 22 | |
| 1000.2.25 | 32 / 22 | |
| 1000.2.23 | 32 / 22 | |
| 1000.2.22 | 32 / 22 | |
| 1000.2.21 | 32 / 22 | |
| 1000.2.20 | 32 / 22 | |
| 1000.2.19 | 32 / 22 | |
| 1000.2.18 | 32 / 22 | |
| 1000.2.17 | 32 / 22 | |
| 1000.2.16 | 32 / 22 | |
| 1000.2.14 | 32 / 22 | |
| 1000.2.13 | 32 / 22 | |
| 1000.2.12 | 32 / 22 | |
| 1000.2.11 | 32 / 22 | |
| 1000.2.10 | 32 / 22 | |
| 1000.2.9 | 32 / 22 | |
| 1000.2.7 | 32 / 21 | |
| 1000.2.6 | 32 / 21 | |
| 1000.2.5 | 32 / 21 | |
| 1000.2.4 | 32 / 21 | |
| 1000.2.3 | 32 / 21 | |
| 1000.2.2 | 32 / 21 | |
| 1000.2.1 | 32 / 21 | |
| 1000.2.0 | 32 / 21 | |
| 1000.1.22 | 31 / 21 | |
| 1000.1.21 | 31 / 21 | |
| 1000.1.20 | 31 / 21 | |
| 1000.1.19 | 31 / 21 | |
| 1000.1.18 | 31 / 21 | |
| 1000.1.17 | 31 / 21 | |
| 1000.1.16 | 31 / 21 | |
| 1000.1.15 | 31 / 21 | |
| 1000.1.14 | 31 / 21 | |
| 1000.1.13 | 31 / 21 | |
| 1000.1.12 | 31 / 21 | |
| 1000.1.11 | 31 / 21 | |
| 1000.1.10 | 31 / 21 | |
| 1000.1.9 | 31 / 21 | |
| 1000.1.8 | 31 / 21 | |
| 1000.1.7 | 31 / 21 | |
| 1000.1.6 | 31 / 21 | |
| 1000.1.5 | 31 / 21 | |
| 1000.1.4 | 31 / 21 | |
| 1000.1.3 | 30 / 20 | |
| 1000.1.2 | 30 / 20 | |
| 1000.1.1 | 30 / 20 | |
| 1000.1.0 | 30 / 20 | |
| 1000.0.1 | 30 / 20 | |
| 1000.0.0 | 30 / 20 |
v1000.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1000.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1000.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.