← Home

@wildix/xbees-kite-client

npm

@wildix/xbees-kite-client client

39
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
provenance publisher-changed AI (provenance): Publisher change is within the same @wildix org; new publisher has clean track record and no code changes. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers appear to be internal @wildix team members; consistent with org-level team management. ai
phantom-deps phantom-dep:@smithy/middleware-stack AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. ai
phantom-deps phantom-dep:@aws-sdk/middleware-logger AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. ai
phantom-deps phantom-dep:@aws-sdk/types AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. ai
phantom-deps phantom-dep:@aws-sdk/middleware-host-header AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. ai
phantom-deps phantom-dep:@aws-sdk/middleware-recursion-detection AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. ai
phantom-deps phantom-dep:@smithy/invalid-dependency AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. ai
phantom-deps phantom-dep:@smithy/config-resolver AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. ai

Versions (showing 39 of 39)

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.5.0 34 / 6
1.4.1 34 / 6
1.4.0 34 / 6
1.3.3 34 / 6
1.3.2 34 / 6
1.3.1 34 / 6
1.3.0 34 / 6
1.2.3 34 / 6
1.2.2 34 / 6
1.2.1 34 / 6
1.2.0 34 / 6
1.1.1 34 / 6
1.1.0 34 / 6
1.0.23 34 / 6
1.0.22 34 / 6
1.0.21 34 / 6
1.0.20 34 / 6
1.0.19 34 / 6
1.0.18 34 / 6
1.0.17 34 / 6
1.0.15 30 / 6
1.0.14 30 / 6
1.0.13 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 30 / 6
1.0.5 30 / 6
1.0.4 30 / 6
1.0.3 30 / 6
1.0.2 30 / 6
1.0.1 30 / 6

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 → mike.lozinsky (on 2026-07-21, known maintainer) provenance

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

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: mike.lozinsky → 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 (mike.lozinsky) 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 → mike.lozinsky (on 2026-07-15, known maintainer) provenance

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

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

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.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. Consider requesting the maintainer enable provenance via CI/CD.

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.