← Home

@yao-pkg/pkg-fetch

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

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

roberts_landon1ru4l

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Build tool passes env to subprocess for Node.js compilation; standard pattern, not exfiltration. ai
semgrep semgrep:child-process-import AI (semgrep): pkg-fetch is a build tool that compiles Node.js binaries; child_process use is inherent to its function. ai

Versions (showing 3 of 3)

Version Deps Published
3.5.33 7 / 20
3.5.32 7 / 20
3.5.31 7 / 20

v3.5.33

2 findings
HIGH env-spread: lib-es5/build.js:176 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/yao-pkg/pkg-fetch/blob/873add6e109eea7092bbe7a0dfe9b9b4bf342abb/lib-es5/build.js#L176 174 | await (0, utils_1.spawn)('cmd', args, { 175 | cwd: nodePath, > 176 | env: { ...process.env, config_flags: config_flags.join(' ') }, 177 | stdio: 'inherit', 178 | });

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.

v3.5.32

1 finding
LOW No provenance attestation provenance

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

v3.5.31

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.