@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 1.3.17 | 0 / 5 | |
| 1.3.16 | 0 / 5 | |
| 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 | |
| 1.2.37 | 0 / 5 | |
| 1.2.36 | 0 / 5 | |
| 1.2.34 | 0 / 5 | |
| 1.2.33 | 0 / 5 | |
| 1.2.32 | 0 / 5 | |
| 1.2.31 | 0 / 5 | |
| 1.2.30 | 0 / 5 | |
| 1.2.29 | 0 / 5 | |
| 1.2.28 | 0 / 5 | |
| 1.2.27 | 0 / 5 | |
| 1.2.26 | 0 / 5 | |
| 1.2.24 | 0 / 4 | |
| 1.2.23 | 0 / 4 | |
| 1.2.22 | 0 / 4 | |
| 1.2.21 | 0 / 4 | |
| 1.2.20 | 0 / 4 | |
| 1.2.18 | 0 / 4 | |
| 1.2.16 | 0 / 4 | |
| 1.2.15 | 0 / 4 | |
| 1.2.14 | 1 / 4 | |
| 1.2.13 | 1 / 4 | |
| 1.2.12 | 1 / 4 | |
| 1.2.11 | 1 / 4 | |
| 1.2.10 | 1 / 4 | |
| 1.2.9 | 1 / 4 | |
| 1.2.8 | 1 / 4 | |
| 1.2.6 | 0 / 4 | |
| 1.2.5 | 0 / 4 | |
| 1.2.4 | 0 / 4 | |
| 1.2.1 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.21 | 0 / 3 | |
| 1.1.20 | 0 / 3 | |
| 1.1.17 | 0 / 3 | |
| 1.1.16 | 0 / 3 | |
| 1.1.15 | 0 / 3 | |
| 1.1.14 | 0 / 3 |
v1.3.17
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 (alex_dubovskiy) than the most recent previously approved version (irenekvachuk) on 2026-07-21, but alex_dubovskiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.3.16
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 (irenekvachuk) than the most recent previously approved version (alex_dubovskiy) on 2026-07-13, but irenekvachuk is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.37
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 (alex_dubovskiy) than the most recent previously approved version (dmytro.renkas) on 2025-04-08, but alex_dubovskiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.36
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 (alex_dubovskiy) than the most recent previously approved version (dmytro.renkas) on 2025-02-18, but alex_dubovskiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
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 (dmytro.renkas) than the most recent previously approved version (alex_dubovskiy) on 2025-01-15, but dmytro.renkas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.31
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 (dmytro.renkas) than the most recent previously approved version (alex_dubovskiy) on 2024-12-22, but dmytro.renkas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.30
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 (alex_dubovskiy) than the most recent previously approved version (dmytro.renkas) on 2024-11-04, but alex_dubovskiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.29
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 (dmytro.renkas) than the most recent previously approved version (alex_dubovskiy) on 2024-10-15, but dmytro.renkas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
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 (alex_dubovskiy) than the most recent previously approved version (dmytro.renkas) on 2024-08-02, but alex_dubovskiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.23
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 (dmytro.renkas) than the most recent previously approved version (alex_dubovskiy) on 2024-08-02, but dmytro.renkas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
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 (alex_dubovskiy) than the most recent previously approved version (dmytro.renkas) on 2024-08-02, but alex_dubovskiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.20
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 (alex_dubovskiy) than the most recent previously approved version (dmytro.renkas) on 2024-08-01, but alex_dubovskiy is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
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 (dmytro.renkas) than the most recent previously approved version (xbeesdcoder) on 2024-07-03, but dmytro.renkas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.12
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 (dmytro.renkas) than the most recent previously approved version (xbeesdcoder) on 2024-07-03, but dmytro.renkas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.11
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 (xbeesdcoder) than the most recent previously approved version (dmytro.renkas) on 2024-07-01, but xbeesdcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
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 (dmytro.renkas) than the most recent previously approved version (xbeesdcoder) on 2024-06-13, but dmytro.renkas is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
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 (xbeesdcoder) than the most recent previously approved version (alex_dubovskiy) on 2024-04-12, but xbeesdcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.