@wildix/xbees-users-client
@wildix/xbees-users-client client
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/config-resolver | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-logger | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@smithy/invalid-dependency | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-host-header | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-recursion-detection | AI (phantom-deps): AWS SDK convention-loaded dependency; stable for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 34 / 6 | |
| 1.3.0 | 34 / 6 | |
| 1.2.9 | 34 / 6 | |
| 1.2.8 | 34 / 6 | |
| 1.2.7 | 34 / 6 | |
| 1.2.6 | 34 / 6 | |
| 1.2.5 | 34 / 6 | |
| 1.2.4 | 34 / 6 | |
| 1.2.3 | 34 / 6 | |
| 1.2.2 | 34 / 6 | |
| 1.1.0 | 34 / 6 | |
| 1.0.54 | 34 / 6 | |
| 1.0.53 | 34 / 6 | |
| 1.0.52 | 34 / 6 | |
| 1.0.51 | 34 / 6 | |
| 1.0.50 | 34 / 6 | |
| 1.0.49 | 34 / 6 | |
| 1.0.48 | 34 / 6 | |
| 1.0.47 | 34 / 6 | |
| 1.0.46 | 34 / 6 | |
| 1.0.45 | 34 / 6 | |
| 1.0.44 | 34 / 6 | |
| 1.0.43 | 34 / 6 | |
| 1.0.42 | 34 / 6 | |
| 1.0.41 | 34 / 6 |
v1.3.1
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 (vruban.wildix) than the most recent previously approved version (mike.lozinsky) on 2026-06-01, but vruban.wildix 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.