← Home

@pnpm/run-npm

3
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
semgrep semgrep:env-spread AI (semgrep): Intentional pattern: package runs npm subprocesses and must propagate env; spreading process.env is correct here. ai

Versions (showing 3 of 3)

Version Deps Published
1000.1.1 2 / 2
1000.1.0 2 / 2
1000.0.0 2 / 2

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