← Home

@wildix/wda-stream-client

npm

@wildix/wda-stream-client client

100
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
source-diff obfuscated-file:dist-cjs/schemas/schemas_0.js AI (source-diff): Smithy SDK codegen output with long export lines; not obfuscation. ai
source-diff obfuscated-file:dist-es/schemas/schemas_0.js AI (source-diff): Smithy SDK codegen pattern using short string-constant aliases; not obfuscation. 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:@aws-sdk/types AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client libraries. 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
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:@smithy/config-resolver AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS SDK clients. ai

Versions (showing 100 of 120)

Version Deps Published
4.0.9 8 / 6
4.0.7 8 / 6
4.0.6 8 / 6
4.0.5 8 / 6
4.0.3 8 / 6
4.0.2 8 / 6
4.0.1 8 / 6
3.1.69 8 / 6
1.1.72 34 / 6
1.1.71 34 / 6
1.1.70 34 / 6
1.1.69 34 / 6
1.1.67 34 / 6
1.1.66 34 / 6
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.48 34 / 6
1.1.47 34 / 6
1.1.46 34 / 6
1.1.45 34 / 6
1.1.44 34 / 6
1.1.41 34 / 6
1.1.40 34 / 6
1.1.39 34 / 6
1.1.38 34 / 6
1.1.33 34 / 6
1.1.32 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.19 34 / 6
1.1.18 34 / 6
1.1.16 34 / 6
1.1.15 34 / 6
1.1.14 34 / 6
1.1.13 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
1.0.50 34 / 6
1.0.49 34 / 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 / 6
1.0.38 30 / 6
1.0.37 30 / 6
1.0.36 30 / 6
1.0.35 30 / 6
1.0.34 30 / 6
1.0.33 30 / 6
1.0.32 30 / 6
1.0.31 30 / 6
1.0.30 30 / 6
1.0.29 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
Showing 100 of 120 Next page →

v4.0.9

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 → ilya.chantsov (on 2026-07-23, known maintainer) provenance

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

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: ilya.chantsov → 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 (ilya.chantsov) 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.6

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 → ilya.chantsov (on 2026-07-16, known maintainer) provenance

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

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 → 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 (vyacheslav.tkachenko) 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.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: marina.tsymbal → vyacheslav.tkachenko (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (vyacheslav.tkachenko) than the most recent previously approved version (marina.tsymbal) on 2026-07-15, but vyacheslav.tkachenko 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 → marina.tsymbal (on 2026-07-10, known maintainer) provenance

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

v4.0.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: marina.tsymbal → vruban.wildix (on 2026-07-04, known maintainer) provenance

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

v3.1.69

4 findings
HIGH New obfuscated file: dist-cjs/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist-es/schemas/schemas_0.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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-30, 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-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.1.72

1 finding
LOW No provenance attestation provenance

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

v1.1.71

1 finding
LOW No provenance attestation provenance

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

v1.1.70

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 → marina.tsymbal (on 2026-07-02, known maintainer) provenance

This version was published by a different npm account (marina.tsymbal) than the most recent previously approved version (gennadiy.ganchev) on 2026-07-02, 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.1.48

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-03-16, 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-03-16, 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.47

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-03-16, 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-03-16, 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.40

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-03-11, 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-03-11, 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.39

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-03-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-03-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.33

1 finding
LOW No provenance attestation provenance

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

v1.1.32

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-03-02, 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-03-02, 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.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: gennadiy.ganchev → lorans.chirko (on 2026-02-04, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v1.1.13

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 2025-11-24, known maintainer) provenance

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.