← Home

@wildix/wda-stream-client

npm

@wildix/wda-stream-client client

48
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.soloviovirenekvachukalex.fedusvlad.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 framework-scoped package; loaded by convention in AWS client libraries. ai
phantom-deps phantom-dep:@smithy/config-resolver AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. ai
phantom-deps phantom-dep:@smithy/middleware-stack AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/middleware-logger AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. ai
phantom-deps phantom-dep:@smithy/invalid-dependency AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/middleware-host-header AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. ai
phantom-deps phantom-dep:@aws-sdk/middleware-recursion-detection AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. ai

Versions (showing 48 of 48)

Version Deps Published
1.1.65 34 / 6
1.1.64 34 / 6
1.1.63 34 / 6
1.1.62 34 / 6
1.1.61 34 / 6
1.1.60 34 / 6
1.1.59 34 / 6
1.1.58 34 / 6
1.1.57 34 / 6
1.1.56 34 / 6
1.1.55 34 / 6
1.1.49 34 / 6
1.1.46 34 / 6
1.1.45 34 / 6
1.1.44 34 / 6
1.1.41 34 / 6
1.1.38 34 / 6
1.1.31 34 / 6
1.1.30 34 / 6
1.1.29 34 / 6
1.1.28 34 / 6
1.1.27 34 / 6
1.1.26 34 / 6
1.1.25 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.18 34 / 6
1.1.16 34 / 6
1.1.15 34 / 6
1.1.12 34 / 6
1.1.11 34 / 6
1.1.6 34 / 6
1.1.4 34 / 6
1.1.3 34 / 6
1.1.1 34 / 6
1.0.63 34 / 6
1.0.61 34 / 6
1.0.60 34 / 6
1.0.59 34 / 6
1.0.57 34 / 6
1.0.56 34 / 6
1.0.55 34 / 6
1.0.54 34 / 6
1.0.53 34 / 6
1.0.51 34 / 6

v1.1.65

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 → gennadiy.ganchev (on 2026-06-05, known maintainer) provenance

This version was published by a different npm account (gennadiy.ganchev) than the most recent previously approved version (vruban.wildix) on 2026-06-05, but gennadiy.ganchev 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.64

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: gennadiy.ganchev → vruban.wildix (on 2026-06-04, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.1.62

1 finding
LOW No provenance attestation provenance

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

v1.1.61

1 finding
LOW No provenance attestation provenance

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

v1.1.60

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 → gennadiy.ganchev (on 2026-06-02, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.1.58

1 finding
LOW No provenance attestation provenance

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

v1.1.57

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: gennadiy.ganchev → vruban.wildix (on 2026-06-01, known maintainer) provenance

This version was published by a different npm account (vruban.wildix) than the most recent previously approved version (gennadiy.ganchev) 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.1.56

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: vyacheslav.tkachenko → gennadiy.ganchev (on 2026-05-29, known maintainer) provenance

This version was published by a different npm account (gennadiy.ganchev) than the most recent previously approved version (vyacheslav.tkachenko) on 2026-05-29, but gennadiy.ganchev 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.55

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: vyacheslav.tkachenko → gennadiy.ganchev (on 2026-05-22, known maintainer) provenance

This version was published by a different npm account (gennadiy.ganchev) than the most recent previously approved version (vyacheslav.tkachenko) on 2026-05-22, but gennadiy.ganchev 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.46

1 finding
LOW No provenance attestation provenance

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

v1.1.45

1 finding
LOW No provenance attestation provenance

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

v1.1.44

1 finding
LOW No provenance attestation provenance

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

v1.1.41

1 finding
LOW No provenance attestation provenance

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

v1.1.38

1 finding
LOW No provenance attestation provenance

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

v1.1.31

1 finding
LOW No provenance attestation provenance

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

v1.1.30

1 finding
LOW No provenance attestation provenance

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

v1.1.29

1 finding
LOW No provenance attestation provenance

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

v1.1.28

1 finding
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.25

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

1 finding
LOW No provenance attestation provenance

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

v1.1.16

1 finding
LOW No provenance attestation provenance

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

v1.1.15

1 finding
LOW No provenance attestation provenance

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

v1.1.12

1 finding
LOW No provenance attestation provenance

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

v1.1.11

1 finding
LOW No provenance attestation provenance

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

v1.1.6

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

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.0.63

1 finding
LOW No provenance attestation provenance

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

v1.0.61

1 finding
LOW No provenance attestation provenance

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

v1.0.60

1 finding
LOW No provenance attestation provenance

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

v1.0.59

1 finding
LOW No provenance attestation provenance

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

v1.0.57

1 finding
LOW No provenance attestation provenance

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

v1.0.56

1 finding
LOW No provenance attestation provenance

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

v1.0.55

1 finding
LOW No provenance attestation provenance

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

v1.0.54

1 finding
LOW No provenance attestation provenance

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

v1.0.53

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

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.