@yao-pkg/pkg-fetch
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance; legitimate automation pattern for this package. | ai | |
| 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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.6.3 | 7 / 20 | |
| 3.6.2 | 7 / 20 | |
| 3.6.1 | 7 / 20 | |
| 3.5.34 | 7 / 20 | |
| 3.5.33 | 7 / 20 | |
| 3.5.32 | 7 / 20 | |
| 3.5.31 | 7 / 20 | |
| 3.5.30 | 7 / 20 | |
| 3.5.29 | 7 / 20 | |
| 3.5.28 | 7 / 20 | |
| 3.5.27 | 7 / 20 | |
| 3.5.26 | 7 / 20 | |
| 3.5.25 | 7 / 20 | |
| 3.5.24 | 7 / 20 | |
| 3.5.23 | 7 / 20 | |
| 3.5.22 | 7 / 20 |
v3.6.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.34
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.33
2 findingsSpreading 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 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.