← Home

@pnpm/modules-cleaner

npm Repository Homepage
36
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 canonical pnpm author; pnpmuser→zkochan transition is a known account consolidation, not a takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects pnpm's internal package versioning cadence, not suspicious activity; consistent with legitimate monorepo maintenance. ai

Versions (showing 36 of 36)

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

v1001.0.12

1 finding
LOW No provenance attestation provenance

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

v1001.0.11

1 finding
LOW No provenance attestation provenance

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

v1001.0.10

1 finding
LOW No provenance attestation provenance

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

v1001.0.9

1 finding
LOW No provenance attestation provenance

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

v1001.0.8

1 finding
LOW No provenance attestation provenance

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

v1001.0.7

1 finding
LOW No provenance attestation provenance

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

v1001.0.6

1 finding
LOW No provenance attestation provenance

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

v1001.0.5

1 finding
LOW No provenance attestation provenance

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

v1001.0.4

1 finding
LOW No provenance attestation provenance

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

v1001.0.3

1 finding
LOW No provenance attestation provenance

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

v1001.0.2

1 finding
LOW No provenance attestation provenance

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

v1001.0.1

1 finding
LOW No provenance attestation provenance

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

v1001.0.0

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.