@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, 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 |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Deprecation shim intentionally re-exports a new package; size drop matches stated purpose. | ai | |
| dependencies | unvetted-dep:@ariestools/threads | AI (dependencies): Successor package explicitly named as replacement in package.json deprecation notice. | ai | |
| 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 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 1 / 12 | |
| 8.0.0 | 1 / 12 | |
| 7.0.8 | 1 / 17 | |
| 7.0.7 | 1 / 17 | |
| 7.0.6 | 1 / 17 | |
| 7.0.5 | 1 / 17 | |
| 7.0.4 | 1 / 17 | |
| 7.0.3 | 1 / 17 | |
| 7.0.2 | 1 / 13 | |
| 7.0.1 | 1 / 13 | |
| 7.0.0 | 1 / 13 | |
| 6.1.4 | 1 / 13 | |
| 6.1.3 | 1 / 12 | |
| 6.1.1 | 1 / 12 | |
| 6.1.0 | 1 / 12 | |
| 6.0.10 | 1 / 12 | |
| 6.0.9 | 1 / 12 | |
| 6.0.8 | 1 / 12 | |
| 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.1.1 | 1 / 11 | |
| 5.1.0 | 1 / 12 | |
| 5.0.102 | 1 / 12 | |
| 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 |
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.102
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-04, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.