join
The join / synchronize module of FuturesJS (Browser, Node.js, Bower, and Pakmanager)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): 'join' is a 14+ year old async/flow-control utility in the FuturesJS ecosystem; the name similarity to 'joi' is purely coincidental — different purpose, different author, different domain. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 0 | |
| 2.3.2 | 1 / 0 | |
| 2.3.1 | 1 / 0 | |
| 2.3.0 | 1 / 0 | |
| 2.1.1 | 1 / 0 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsPackage name 'join' is 1 edit(s) away from popular package 'joi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.