← Home

@wildix/xbees-users-client

npm

@wildix/xbees-users-client client

64
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

konstantin.tkachenko.wildixvruban.wildixxbeesdcoderdmytro.renkasvyacheslav.tkachenkomarina.tsymbalmike.lozinskyvladimir.gorobets.wildixalex_dubovskiysergey.dartchukirenekvachukgennadiy.ganchevalex.soloviovalex.fedusilya.chantsovvlad.chernehamax.ivanov.wildixlorans.chirkovit_bal_wildixvitaliy.buziyanalex.pokidinvyacheslav.korotkovdimitri.voronov

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 64 of 64)

Version Deps Published
4.0.4 8 / 6
4.0.3 8 / 6
4.0.2 8 / 6
4.0.1 8 / 6
3.1.1 8 / 6
1.4.0 34 / 6
1.3.2 34 / 6
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
1.0.40 34 / 6
1.0.39 34 / 6
1.0.38 30 / 6
1.0.35 30 / 6
1.0.34 30 / 6
1.0.28 30 / 6
1.0.27 30 / 6
1.0.26 30 / 6
1.0.25 30 / 6
1.0.24 30 / 6
1.0.23 30 / 6
1.0.22 30 / 6
1.0.21 30 / 6
1.0.20 30 / 6
1.0.19 30 / 6
1.0.18 30 / 6
1.0.17 30 / 6
1.0.16 30 / 6
1.0.15 30 / 6
1.0.14 30 / 6
1.0.12 30 / 6
1.0.11 30 / 6
1.0.10 30 / 6
1.0.9 30 / 6
1.0.8 30 / 6
1.0.7 26 / 8
1.0.6 25 / 8
1.0.5 25 / 8
1.0.4 25 / 8
1.0.3 25 / 8
1.0.2 25 / 8
1.0.1 25 / 8

v4.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vladimir.gorobets.wildix → vruban.wildix (on 2026-07-22, known maintainer) provenance

This version was published by a different npm account (vruban.wildix) than the most recent previously approved version (vladimir.gorobets.wildix) on 2026-07-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.

v4.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: alex.pokidin → vladimir.gorobets.wildix (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (alex.pokidin) 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.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vruban.wildix → alex.pokidin (on 2026-07-14, known maintainer) provenance

This version was published by a different npm account (alex.pokidin) than the most recent previously approved version (vruban.wildix) on 2026-07-14, but alex.pokidin 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
LOW No provenance attestation provenance

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

v3.1.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mike.lozinsky → vruban.wildix (on 2026-06-30, known maintainer) provenance

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.0.40

1 finding
LOW No provenance attestation provenance

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

v1.0.39

1 finding
LOW No provenance attestation provenance

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

v1.0.38

1 finding
LOW No provenance attestation provenance

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

v1.0.35

1 finding
LOW No provenance attestation provenance

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

v1.0.34

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: max_bormot → vruban.wildix (on 2025-03-19, known maintainer) provenance

This version was published by a different npm account (vruban.wildix) than the most recent previously approved version (max_bormot) on 2025-03-19, 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.28

1 finding
LOW No provenance attestation provenance

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

v1.0.27

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: max_bormot → vruban.wildix (on 2025-02-06, known maintainer) provenance

This version was published by a different npm account (vruban.wildix) than the most recent previously approved version (max_bormot) on 2025-02-06, 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.26

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vruban.wildix → max_bormot (on 2025-02-03, known maintainer) provenance

This version was published by a different npm account (max_bormot) than the most recent previously approved version (vruban.wildix) on 2025-02-03, 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.0.25

1 finding
LOW No provenance attestation provenance

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

v1.0.24

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mike.lozinsky → vruban.wildix (on 2024-12-13, known maintainer) provenance

This version was published by a different npm account (vruban.wildix) than the most recent previously approved version (mike.lozinsky) on 2024-12-13, 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.23

1 finding
LOW No provenance attestation provenance

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

v1.0.22

1 finding
LOW No provenance attestation provenance

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

v1.0.21

1 finding
LOW No provenance attestation provenance

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

v1.0.20

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: marina.tsymbal → mike.lozinsky (on 2024-09-16, known maintainer) provenance

This version was published by a different npm account (mike.lozinsky) than the most recent previously approved version (marina.tsymbal) on 2024-09-16, 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.0.19

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: marina.tsymbal → mike.lozinsky (on 2024-09-15, known maintainer) provenance

This version was published by a different npm account (mike.lozinsky) than the most recent previously approved version (marina.tsymbal) on 2024-09-15, 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.0.18

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vruban.wildix → marina.tsymbal (on 2024-08-26, known maintainer) provenance

This version was published by a different npm account (marina.tsymbal) than the most recent previously approved version (vruban.wildix) on 2024-08-26, 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.17

1 finding
LOW No provenance attestation provenance

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

v1.0.16

1 finding
LOW No provenance attestation provenance

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

v1.0.15

1 finding
LOW No provenance attestation provenance

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

v1.0.14

1 finding
LOW No provenance attestation provenance

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

v1.0.12

1 finding
LOW No provenance attestation provenance

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

v1.0.11

1 finding
LOW No provenance attestation provenance

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

v1.0.10

1 finding
LOW No provenance attestation provenance

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

v1.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.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.0.2

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.0.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.