safe-execa
Like execa but prevents binary planting attacks on Windows
2
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
zkochan
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@zkochan/which | AI (dependencies): Scoped package authored by the same publisher (zkochan); consistent with their established ecosystem of utilities. Low risk. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has a strong 3474-day track record with 146 approved packages and 0 rejections. Lack of provenance is not a meaningful risk signal here. | ai |
v0.3.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.
v0.2.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.