@wildix/xbees-connect
This library provides easy communication between x-bees and integrated web applications
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
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.3.15 | 0 / 5 | |
| 1.3.12 | 0 / 5 | |
| 1.3.11 | 0 / 5 | |
| 1.3.10 | 0 / 5 | |
| 1.3.9 | 0 / 5 | |
| 1.3.8 | 0 / 5 | |
| 1.3.3 | 0 / 5 | |
| 1.3.2 | 0 / 5 | |
| 1.3.1 | 0 / 5 | |
| 1.3.0 | 0 / 5 | |
| 1.2.41 | 0 / 5 | |
| 1.2.38 | 0 / 5 |
v1.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.