@wildix/xbees-conversations-client
@wildix/xbees-conversations-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer, no malicious behavior indicated. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Official AWS SDK/Smithy packages matching client's generated dependency set. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change already vetted with strong track record (37/0) since 263 days ago. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same maintainer transition already reflected in publisher track record. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Codegen'd AWS-SDK-style client; large file additions consistent with generated modules. | ai | |
| provenance | no-provenance | AI (provenance): Established @wildix org package; no provenance attestation is consistent across all prior versions. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-recursion-detection | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/config-resolver | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-logger | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/invalid-dependency | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-host-header | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. | ai |
Versions (showing 98 of 98)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 8 / 6 | |
| 4.0.2 | 8 / 6 | |
| 4.0.1 | 8 / 6 | |
| 3.1.1 | 8 / 6 | |
| 1.5.0 | 34 / 6 | |
| 1.4.1 | 34 / 6 | |
| 1.4.0 | 34 / 6 | |
| 1.3.0 | 34 / 6 | |
| 1.2.14 | 34 / 6 | |
| 1.2.13 | 34 / 6 | |
| 1.2.12 | 34 / 6 | |
| 1.2.11 | 34 / 6 | |
| 1.2.10 | 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.2.1 | 34 / 6 | |
| 1.2.0 | 34 / 6 | |
| 1.1.28 | 34 / 6 | |
| 1.1.27 | 34 / 6 | |
| 1.1.26 | 34 / 6 | |
| 1.1.24 | 34 / 6 | |
| 1.1.23 | 34 / 6 | |
| 1.1.22 | 34 / 6 | |
| 1.1.21 | 34 / 6 | |
| 1.1.20 | 34 / 6 | |
| 1.1.19 | 34 / 6 | |
| 1.1.18 | 34 / 6 | |
| 1.1.17 | 34 / 6 | |
| 1.1.16 | 34 / 6 | |
| 1.1.15 | 34 / 6 | |
| 1.1.14 | 34 / 6 | |
| 1.1.13 | 30 / 6 | |
| 1.1.12 | 30 / 6 | |
| 1.1.11 | 30 / 6 | |
| 1.1.10 | 30 / 6 | |
| 1.1.9 | 30 / 6 | |
| 1.1.8 | 30 / 6 | |
| 1.1.7 | 30 / 6 | |
| 1.1.6 | 30 / 6 | |
| 1.1.5 | 30 / 6 | |
| 1.1.4 | 30 / 6 | |
| 1.1.3 | 30 / 6 | |
| 1.1.2 | 30 / 6 | |
| 1.1.1 | 30 / 6 | |
| 1.1.0 | 30 / 6 | |
| 1.0.65 | 30 / 6 | |
| 1.0.64 | 30 / 6 | |
| 1.0.63 | 30 / 6 | |
| 1.0.62 | 30 / 6 | |
| 1.0.61 | 30 / 6 | |
| 1.0.60 | 30 / 6 | |
| 1.0.59 | 30 / 6 | |
| 1.0.58 | 30 / 6 | |
| 1.0.57 | 30 / 6 | |
| 1.0.56 | 30 / 6 | |
| 1.0.55 | 30 / 6 | |
| 1.0.54 | 30 / 6 | |
| 1.0.53 | 30 / 6 | |
| 1.0.52 | 30 / 6 | |
| 1.0.51 | 30 / 6 | |
| 1.0.50 | 30 / 6 | |
| 1.0.49 | 30 / 6 | |
| 1.0.48 | 30 / 6 | |
| 1.0.47 | 30 / 6 | |
| 1.0.46 | 30 / 6 | |
| 1.0.45 | 30 / 6 | |
| 1.0.44 | 30 / 6 | |
| 1.0.43 | 30 / 6 | |
| 1.0.42 | 30 / 6 | |
| 1.0.41 | 30 / 6 | |
| 1.0.40 | 30 / 6 | |
| 1.0.39 | 30 / 7 | |
| 1.0.38 | 30 / 7 | |
| 1.0.37 | 30 / 7 | |
| 1.0.36 | 30 / 7 | |
| 1.0.35 | 26 / 8 | |
| 1.0.34 | 26 / 8 | |
| 1.0.33 | 26 / 8 | |
| 1.0.32 | 26 / 8 | |
| 1.0.31 | 26 / 8 | |
| 1.0.30 | 26 / 8 | |
| 1.0.29 | 26 / 8 | |
| 1.0.28 | 26 / 8 | |
| 1.0.27 | 26 / 8 | |
| 1.0.26 | 26 / 8 | |
| 1.0.25 | 26 / 8 | |
| 1.0.24 | 26 / 8 | |
| 1.0.23 | 26 / 8 | |
| 1.0.22 | 26 / 8 | |
| 1.0.21 | 26 / 8 | |
| 1.0.20 | 26 / 8 | |
| 1.0.18 | 26 / 8 |
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2026-07-16, but vladimir.gorobets.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.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findings[Accepted risk] Package 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-30, 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.2.13
2 findings[Accepted risk] Package 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-03-25, 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.2.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alex.fedus) than the most recent previously approved version (max_bormot) on 2025-12-04, but alex.fedus 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
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: max_bormot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (max_bormot) than the most recent previously approved version (mike.lozinsky) on 2025-04-14, but max_bormot 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.13
2 findings[Accepted risk] Package 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 2025-03-25, 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.1.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike.lozinsky) than the most recent previously approved version (vruban.wildix) on 2025-03-24, but mike.lozinsky 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.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike.lozinsky) than the most recent previously approved version (vruban.wildix) on 2025-03-13, but mike.lozinsky 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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2024-12-04, but vladimir.gorobets.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.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
2 findings[Accepted risk] Package 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 (vladimir.gorobets.wildix) on 2024-11-04, 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.0.60
2 findings[Accepted risk] Package 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 (vladimir.gorobets.wildix) on 2024-11-04, 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.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
2 findingsThis version was published by a different npm account than previous versions on 2024-09-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2024-09-19, but vladimir.gorobets.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.0.56
2 findings[Accepted risk] Package 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 (vladimir.gorobets.wildix) on 2024-08-22, 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.0.55
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2024-08-16, but vladimir.gorobets.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.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
2 findings[Accepted risk] Package 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 (vladimir.gorobets.wildix) on 2024-07-29, 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.0.50
2 findings[Accepted risk] Package 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 (vladimir.gorobets.wildix) on 2024-07-25, 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.0.49
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2024-07-11, but vladimir.gorobets.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.0.48
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marina.tsymbal) than the most recent previously approved version (vruban.wildix) on 2024-07-01, but marina.tsymbal 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.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marina.tsymbal) than the most recent previously approved version (vruban.wildix) on 2024-06-11, but marina.tsymbal 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.0.43
2 findings[Accepted risk] Package 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 (marina.tsymbal) on 2024-06-10, 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.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marina.tsymbal) than the most recent previously approved version (vladimir.gorobets.wildix) on 2024-06-07, but marina.tsymbal 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.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2024-05-30, but vladimir.gorobets.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.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.