← Home

@pnpm/node.fetcher

npm Repository Homepage
34
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

pnpmuserzkochan

Keywords

pnpmpnpm10envnode.js

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): zkochan (Zoltan Kochan) is the primary pnpm maintainer; transition from pnpmuser bot account to zkochan is a known and legitimate pattern for this package family. ai
provenance no-provenance AI (provenance): pnpm monorepo packages are published without Sigstore provenance; this is consistent across all @pnpm/* packages and does not indicate risk. ai

Versions (showing 34 of 34)

Version Deps Published
1001.0.33 8 / 7
1001.0.32 8 / 7
1001.0.31 8 / 7
1001.0.30 8 / 7
1001.0.29 8 / 7
1001.0.28 8 / 7
1001.0.27 8 / 7
1001.0.26 8 / 7
1001.0.25 8 / 7
1001.0.24 8 / 7
1001.0.23 8 / 7
1001.0.22 8 / 7
1001.0.21 8 / 7
1001.0.20 8 / 7
1001.0.19 8 / 7
1001.0.18 8 / 7
1001.0.17 8 / 7
1001.0.16 8 / 7
1001.0.15 8 / 7
1001.0.14 8 / 7
1001.0.13 8 / 7
1001.0.12 8 / 7
1001.0.11 8 / 7
1001.0.10 8 / 7
1001.0.9 8 / 7
1001.0.8 8 / 7
1001.0.7 8 / 7
1001.0.6 8 / 7
1001.0.5 8 / 7
1001.0.4 8 / 7
1001.0.3 8 / 7
1001.0.2 8 / 7
1001.0.1 8 / 6
1001.0.0 8 / 6

v1001.0.33

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1001.0.32

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.