@chainsafe/threads
2
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
wemeetagain
Keywords
threadworkerpoolspawnisomorphicparallelobservableworker_threads
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval("require").resolve("ts-node") is a hardcoded string probe for optional ts-node dependency — not user-controlled input, stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function(sourceCode) implements the documented fromSource worker feature of threads.js — core library functionality, not malicious code execution. | ai | |
| dependencies | unvetted-dep:observable-fns | AI (dependencies): observable-fns is a legitimate, well-known reactive utility that is the documented observable implementation for threads.js. | ai |
v1.11.3
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.