← Home

@wildix/wms-permissions-client

npm

@wildix/wms-permissions-client client

21
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
maintainer-change maintainer-added AI (maintainer-change): New maintainers appear to be @wildix org team members; consistent with org-level team expansion. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of max_bormot alongside addition of multiple org members suggests planned team rotation, not takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by team expansion is consistent with org restructuring; no malicious indicators in the diff. ai
phantom-deps phantom-dep:@aws-sdk/middleware-logger AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. ai
phantom-deps phantom-dep:@smithy/invalid-dependency AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/types AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/middleware-recursion-detection AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. ai
phantom-deps phantom-dep:@aws-sdk/middleware-host-header AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in SDK clients. ai
phantom-deps phantom-dep:@smithy/config-resolver AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients. ai
phantom-deps phantom-dep:@smithy/middleware-stack AI (phantom-deps): Smithy framework-scoped package; loaded by convention in SDK clients. ai

Versions (showing 21 of 21)

Version Deps Published
4.0.3 8 / 6
4.0.2 8 / 6
4.0.1 8 / 6
3.1.14 8 / 6
1.1.13 34 / 6
1.1.12 34 / 6
1.1.11 34 / 6
1.1.9 34 / 6
1.1.8 34 / 6
1.1.7 34 / 6
1.1.6 34 / 6
1.1.4 34 / 6
1.1.3 34 / 6
1.1.2 34 / 6
1.1.1 34 / 6
1.1.0 26 / 8
1.0.5 26 / 8
1.0.4 26 / 8
1.0.3 26 / 8
1.0.2 25 / 8
1.0.1 26 / 8

v4.0.3

1 finding
LOW No provenance attestation provenance

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

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 → 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 (vruban.wildix) 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.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

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 → vladimir.gorobets.wildix (on 2024-04-02, known maintainer) 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, 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.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. Consider requesting the maintainer enable provenance via CI/CD.

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.