@xylabs/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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used for documented fromSource worker feature in threads.js; input is user-supplied worker source code by design. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') is a webpack-compatibility shim to detect worker_threads; not attacker-controlled input. | ai | |
| dependencies | unvetted-dep:is-observable-2-1-0 | AI (dependencies): [email protected] aliased as is-observable-2-1-0 is a known safe utility; alias pattern is stable across versions of this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 6.0.7 | 1 / 12 | |
| 6.0.6 | 1 / 12 | |
| 6.0.5 | 1 / 12 | |
| 6.0.4 | 1 / 12 | |
| 6.0.3 | 1 / 10 | |
| 6.0.2 | 1 / 10 | |
| 6.0.1 | 1 / 10 | |
| 6.0.0 | 1 / 10 | |
| 5.1.5 | 1 / 10 | |
| 5.1.4 | 1 / 10 | |
| 5.1.3 | 1 / 10 | |
| 5.1.2 | 1 / 11 | |
| 5.0.101 | 1 / 12 | |
| 5.0.100 | 1 / 12 | |
| 5.0.99 | 1 / 33 | |
| 5.0.98 | 3 / 9 | |
| 5.0.96 | 4 / 9 | |
| 5.0.78 | 4 / 8 | |
| 5.0.0 | 4 / 9 |
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.