← Home

@pnpm/pnpmfile

npm Repository Homepage

Reading a .pnpmfile.cjs

16
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pnpmuserzkochan

Keywords

pnpmpnpm10

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): This package's purpose is to load user-defined .pnpmfile.cjs hook files at runtime. Dynamic require of a user-supplied path is the intended and correct behavior, not a security risk. ai
dependencies unvetted-dep:path-absolute AI (dependencies): path-absolute is a small, well-known utility with no security concerns; stable false positive for this package. ai
dependencies unvetted-dep:@pnpm/crypto.hash AI (dependencies): Internal @pnpm monorepo package published by the same trusted maintainer (zkochan); unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@pnpm/hooks.types AI (dependencies): Internal @pnpm monorepo package published by the same trusted maintainer (zkochan); unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@pnpm/core-loggers AI (dependencies): Internal @pnpm monorepo package published by the same trusted maintainer (zkochan); unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@pnpm/lockfile.types AI (dependencies): Internal @pnpm monorepo package published by the same trusted maintainer (zkochan); unvetted status is a registry gap, not a security concern. ai
dependencies unvetted-dep:@pnpm/store-controller-types AI (dependencies): Internal @pnpm monorepo package published by the same trusted maintainer (zkochan); unvetted status is a registry gap, not a security concern. ai

Versions (showing 16 of 16)

Version Deps Published
1002.1.12 9 / 4
1002.1.11 9 / 4
1002.1.10 9 / 4
1002.1.9 9 / 4
1002.1.8 9 / 4
1002.1.7 9 / 4
1002.1.6 9 / 4
1002.1.5 9 / 4
1002.1.4 9 / 4
1002.1.3 9 / 4
1002.1.2 9 / 4
1002.1.1 9 / 4
1002.1.0 9 / 4
1002.0.2 9 / 3
1002.0.1 9 / 3
1002.0.0 9 / 3

v1002.1.12

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.

v1002.1.11

1 finding
LOW No provenance attestation provenance

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

v1002.1.10

1 finding
LOW No provenance attestation provenance

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

v1002.1.9

1 finding
LOW No provenance attestation provenance

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

v1002.1.8

1 finding
LOW No provenance attestation provenance

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

v1002.1.7

1 finding
LOW No provenance attestation provenance

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

v1002.1.6

1 finding
LOW No provenance attestation provenance

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

v1002.1.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.

v1002.1.4

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.

v1002.1.3

1 finding
LOW No provenance attestation provenance

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

v1002.1.2

2 findings
HIGH Publisher changed: pnpmuser → zkochan (on 2025-09-29) provenance

This version was published by a different npm account than previous versions on 2025-09-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1002.1.1

1 finding
LOW No provenance attestation provenance

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

v1002.1.0

1 finding
LOW No provenance attestation provenance

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

v1002.0.2

1 finding
LOW No provenance attestation provenance

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

v1002.0.1

1 finding
LOW No provenance attestation provenance

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

v1002.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.