@ardatan/sync-fetch
Synchronous version of the Fetch API
1
Versions
MIT
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
ardatan
Keywords
fetchsync
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): execFileSync is the core mechanism for synchronous HTTP in Node.js — this library spawns a worker process to perform async fetch synchronously. Expected and documented design pattern. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 is used to serialize HTTP response bodies for IPC between the main process and the worker spawned via execFileSync. Standard and necessary for binary-safe inter-process communication. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 2.2M weekly downloads; lack of provenance attestation is common (~88% of npm packages) and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.0.1 | 1 / 14 |
v0.0.1
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.