← Home

@wildix/wms-api-client

npm

@wildix/wms-api-client client

30
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.wildixvitaliy.negrichukxbeesdcoderdmytro.renkasvyacheslav.tkachenkomarina.tsymbalmike.lozinskyvladimir.gorobets.wildixmax_bormotalex_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.

SourceRuleReasonAccepted byWhen
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:@smithy/config-resolver AI (phantom-deps): Smithy framework-scoped package; stable pattern for AWS SDK clients. ai
phantom-deps phantom-dep:@smithy/middleware-stack AI (phantom-deps): Smithy framework-scoped package; stable pattern for AWS SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/middleware-logger AI (phantom-deps): AWS SDK framework-scoped package; stable pattern for AWS SDK clients. ai
phantom-deps phantom-dep:@smithy/invalid-dependency AI (phantom-deps): Smithy framework-scoped package; stable pattern for AWS SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/middleware-host-header AI (phantom-deps): AWS SDK framework-scoped package; stable pattern for AWS SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/middleware-recursion-detection AI (phantom-deps): AWS SDK framework-scoped package; stable pattern for AWS SDK clients. ai

Versions (showing 30 of 30)

Version Deps Published
1.2.3 34 / 6
1.2.2 34 / 6
1.2.1 34 / 6
1.2.0 34 / 6
1.1.27 34 / 6
1.1.26 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 30 / 6
1.1.17 30 / 6
1.1.16 30 / 6
1.1.14 30 / 6
1.1.13 30 / 6
1.1.12 30 / 6
1.1.7 30 / 6
1.1.6 30 / 6
1.1.5 30 / 6
1.1.4 30 / 6
1.1.3 30 / 7
1.1.2 26 / 8
1.1.1 26 / 8
1.1.0 26 / 8
1.0.5 26 / 8
1.0.4 26 / 8
1.0.3 26 / 8
1.0.1 26 / 8

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: vyacheslav.tkachenko → vladimir.gorobets.wildix (on 2025-04-14, 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 2025-04-14, 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.

v1.1.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: sergey.dartchuk → vyacheslav.tkachenko (on 2025-03-12, known maintainer) provenance

This version was published by a different npm account (vyacheslav.tkachenko) than the most recent previously approved version (sergey.dartchuk) on 2025-03-12, 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.

v1.1.17

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

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: sergey.dartchuk → vyacheslav.tkachenko (on 2025-02-27, known maintainer) provenance

This version was published by a different npm account (vyacheslav.tkachenko) than the most recent previously approved version (sergey.dartchuk) on 2025-02-27, 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.

v1.1.13

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

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 → sergey.dartchuk (on 2024-11-11, known maintainer) provenance

This version was published by a different npm account (sergey.dartchuk) than the most recent previously approved version (mike.lozinsky) on 2024-11-11, but sergey.dartchuk 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.7

2 findings
HIGH Publisher changed: mike.lozinsky → vyacheslav.tkachenko (on 2024-09-10) provenance

This version was published by a different npm account than previous versions on 2024-09-10. 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.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.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 2024-07-23, 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 2024-07-23, 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.1.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.1.2

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

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

2 findings
MEDIUM Publisher changed: vruban.wildix → vladimir.gorobets.wildix (on 2024-04-02, unremoved on npm for 844d) provenance

This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2024-04-02. It has since remained available on npm for 844 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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