← Home

@pnpm/workspace.find-packages

npm Repository Homepage
72
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

pnpmpnpm10

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): zkochan is the primary pnpm maintainer (3475 days history, 199 approved packages). The pnpmuser→zkochan transition reflects a legitimate shift from CI bot publishing back to the original maintainer, not a compromise. ai
provenance no-provenance AI (provenance): Official pnpm monorepo package published by the established pnpmuser account; lack of Sigstore provenance is not a meaningful risk signal here. ai

Versions (showing 72 of 72)

Version Deps Published
1000.0.71 5 / 3
1000.0.70 5 / 3
1000.0.69 5 / 3
1000.0.68 5 / 3
1000.0.67 5 / 3
1000.0.66 5 / 3
1000.0.65 5 / 3
1000.0.64 5 / 3
1000.0.63 5 / 3
1000.0.62 5 / 3
1000.0.61 5 / 3
1000.0.60 5 / 3
1000.0.59 5 / 3
1000.0.58 5 / 3
1000.0.57 5 / 3
1000.0.56 5 / 3
1000.0.55 5 / 3
1000.0.54 5 / 3
1000.0.53 5 / 3
1000.0.52 5 / 3
1000.0.51 5 / 3
1000.0.50 5 / 3
1000.0.49 5 / 3
1000.0.48 5 / 3
1000.0.47 5 / 3
1000.0.46 5 / 3
1000.0.45 5 / 3
1000.0.44 5 / 3
1000.0.43 5 / 3
1000.0.42 5 / 3
1000.0.41 5 / 3
1000.0.40 5 / 3
1000.0.39 5 / 3
1000.0.38 5 / 3
1000.0.37 5 / 3
1000.0.36 5 / 3
1000.0.35 5 / 3
1000.0.34 5 / 3
1000.0.33 5 / 3
1000.0.32 5 / 3
1000.0.31 5 / 3
1000.0.30 5 / 3
1000.0.29 5 / 3
1000.0.28 5 / 3
1000.0.27 5 / 3
1000.0.26 5 / 3
1000.0.25 5 / 3
1000.0.24 5 / 3
1000.0.23 5 / 3
1000.0.22 5 / 3
1000.0.21 5 / 3
1000.0.20 5 / 3
1000.0.19 5 / 3
1000.0.18 5 / 3
1000.0.17 5 / 3
1000.0.16 5 / 3
1000.0.15 5 / 3
1000.0.14 5 / 3
1000.0.13 5 / 3
1000.0.12 5 / 3
1000.0.11 5 / 3
1000.0.10 5 / 3
1000.0.9 5 / 3
1000.0.8 5 / 3
1000.0.7 5 / 3
1000.0.6 5 / 3
1000.0.5 4 / 3
1000.0.4 4 / 3
1000.0.3 4 / 3
1000.0.2 4 / 3
1000.0.1 4 / 3
1000.0.0 4 / 3

v1000.0.71

1 finding
INFO No provenance attestation provenance

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

v1000.0.22

1 finding
INFO No provenance attestation provenance

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

v1000.0.21

1 finding
INFO No provenance attestation provenance

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

v1000.0.20

1 finding
INFO No provenance attestation provenance

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

v1000.0.19

1 finding
INFO No provenance attestation provenance

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

v1000.0.18

1 finding
INFO No provenance attestation provenance

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

v1000.0.17

1 finding
INFO No provenance attestation provenance

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

v1000.0.16

1 finding
INFO No provenance attestation provenance

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

v1000.0.15

1 finding
INFO No provenance attestation provenance

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

v1000.0.14

1 finding
INFO No provenance attestation provenance

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

v1000.0.13

1 finding
INFO No provenance attestation provenance

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

v1000.0.12

1 finding
INFO No provenance attestation provenance

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

v1000.0.11

1 finding
INFO No provenance attestation provenance

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

v1000.0.10

1 finding
INFO No provenance attestation provenance

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

v1000.0.9

1 finding
INFO No provenance attestation provenance

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

v1000.0.8

1 finding
INFO No provenance attestation provenance

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

v1000.0.7

1 finding
INFO No provenance attestation provenance

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

v1000.0.6

1 finding
INFO No provenance attestation provenance

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

v1000.0.5

1 finding
INFO No provenance attestation provenance

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

v1000.0.4

1 finding
INFO No provenance attestation provenance

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

v1000.0.3

1 finding
INFO No provenance attestation provenance

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

v1000.0.2

1 finding
INFO No provenance attestation provenance

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

v1000.0.1

1 finding
INFO No provenance attestation provenance

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

v1000.0.0

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.