← Home

@pnpm/store-path

npm Repository Homepage

Resolves the pnpm store path

4
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

pnpmuserzkochan

Keywords

pnpmpnpm10store

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:can-link AI (dependencies): can-link is a stable pnpm ecosystem utility dependency present in prior approved versions; no malicious signals. ai
dependencies unvetted-dep:path-temp AI (dependencies): path-temp is a stable pnpm ecosystem utility dependency present in prior approved versions; no malicious signals. ai
dependencies unvetted-dep:root-link-target AI (dependencies): root-link-target is a stable pnpm ecosystem utility dependency present in prior approved versions; no malicious signals. ai
provenance no-provenance AI (provenance): pnpm monorepo packages historically lack Sigstore provenance; this is consistent across all @pnpm/* packages and not a security concern for this well-established publisher. ai

Versions (showing 4 of 4)

Version Deps Published
1000.0.6 8 / 8
1000.0.5 8 / 8
1000.0.4 8 / 7
1000.0.3 8 / 7

v1000.0.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1000.0.5

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.

v1000.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1000.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.