@rushstack/rush-pnpm-kit-v8
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
rushstack-adminodspnpmoctogonzmicrosoft1es
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pnpm/dependency-path-pnpm-v8 | AI (dependencies): Aliased official @pnpm/dependency-path package, standard rush-pnpm-kit pattern. | ai | |
| dependencies | unvetted-dep:@pnpm/lockfile-file-pnpm-lock-v6 | AI (dependencies): Aliased official @pnpm/lockfile-file package, standard rush-pnpm-kit pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Rushstack build-tool package; sparse metadata is normal for this monorepo family. | ai |
v0.2.21
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.