@chainsafe/threads
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
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 |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.11.3 | 4 / 28 | |
| 1.11.2 | 4 / 28 | |
| 1.11.1 | 5 / 28 | |
| 1.11.0 | 5 / 28 | |
| 1.10.0 | 5 / 28 | |
| 1.9.0 | 5 / 28 | |
| 1.8.0 | 5 / 28 |
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.