@wildix/xbees-conversations-client Apache-2.0 27 versions

@wildix/xbees-conversations-client

npm

@wildix/xbees-conversations-client client

27

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

konstantin.tkachenko.wildixvruban.wildixvitaliy.negrichukxbeesdcoderdmytro.renkasvyacheslav.tkachenkomarina.tsymbalmike.lozinskyvladimir.gorobets.wildixalex_dubovskiysergey.dartchukgennadiy.ganchevalex.soloviovalex.fedusvlad.chernehamax.ivanov.wildixlorans.chirkovit_bal_wildixvitaliy.buziyanalex.pokidinvyacheslav.korotkovdimitri.voronov

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established @wildix org package; no provenance attestation is consistent across all prior versions.	ai	2026/05/11
phantom-deps	phantom-dep:@smithy/config-resolver	AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients.	ai	2026/04/29
phantom-deps	phantom-dep:@smithy/middleware-stack	AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients.	ai	2026/04/29
phantom-deps	phantom-dep:@aws-sdk/middleware-logger	AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients.	ai	2026/04/29
phantom-deps	phantom-dep:@aws-sdk/types	AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients.	ai	2026/04/29
phantom-deps	phantom-dep:@aws-sdk/middleware-host-header	AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients.	ai	2026/04/29
phantom-deps	phantom-dep:@aws-sdk/middleware-recursion-detection	AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients.	ai	2026/04/29
phantom-deps	phantom-dep:@smithy/invalid-dependency	AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients.	ai	2026/04/29

Versions (showing 27 of 27)

Version	Deps	Published
1.4.0	34 / 6	2026-05-01
1.3.0	34 / 6	2026-04-02
1.2.14	34 / 6	2026-03-31
1.2.12	34 / 6	2026-03-17
1.2.11	34 / 6	2026-03-16
1.2.10	34 / 6	2026-03-16
1.2.9	34 / 6	2026-03-16
1.2.8	34 / 6	2026-03-16
1.2.7	34 / 6	2026-03-16
1.2.6	34 / 6	2026-03-12
1.2.4	34 / 6	2025-11-24
1.2.3	34 / 6	2025-11-19
1.2.2	34 / 6	2025-11-14
1.2.1	34 / 6	2025-11-14
1.1.28	34 / 6	2025-10-09
1.1.27	34 / 6	2025-09-24
1.1.26	34 / 6	2025-08-21
1.1.24	34 / 6	2025-08-13
1.1.23	34 / 6	2025-08-12
1.1.22	34 / 6	2025-07-31
1.1.21	34 / 6	2025-07-21
1.1.20	34 / 6	2025-07-21
1.1.19	34 / 6	2025-06-25
1.1.18	34 / 6	2025-06-19
1.1.17	34 / 6	2025-06-18
1.1.16	34 / 6	2025-06-17
1.1.15	34 / 6	2025-06-16

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.2

2 findings

HIGH Publisher changed: mike.lozinsky → max_bormot (on 2025-11-14) provenance

This version was published by a different npm account than previous versions on 2025-11-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.28

2 findings

HIGH Publisher changed: max_bormot → mike.lozinsky (on 2025-10-09) provenance

This version was published by a different npm account than previous versions on 2025-10-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.