← Home

@wildix/auth-utils

npm Repository Homepage

Auth Utils for Wildix SDK

25
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.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
bogus-package bogus-package AI (bogus-package): Sparse README only; established scoped SDK package, no functional risk. ai
maintainer-change maintainer-added AI (maintainer-change): Publisher transition predates this version; account has solid subsequent track record. ai
phantom-deps phantom-dep:qs AI (phantom-deps): qs is a declared runtime dep used transitively or via config; stable false positive for this package. ai

Versions (showing 25 of 25)

Version Deps Published
4.0.1 5 / 8
2.0.2 5 / 8
2.0.0 5 / 7
1.1.1 5 / 7
1.0.22 5 / 7
1.0.21 5 / 7
1.0.20 5 / 7
1.0.19 6 / 8
1.0.18 6 / 8
1.0.17 6 / 8
1.0.16 6 / 8
1.0.14 6 / 8
1.0.13 6 / 8
1.0.12 5 / 7
1.0.11 6 / 7
1.0.10 6 / 7
1.0.9 6 / 7
1.0.8 6 / 7
1.0.7 5 / 7
1.0.6 5 / 7
1.0.5 4 / 7
1.0.4 4 / 7
1.0.3 4 / 7
1.0.2 4 / 7
1.0.1 4 / 7

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.

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.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: 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.21

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-08-29, 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-08-29, 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.14

2 findings
HIGH Publisher changed: sergey.dartchuk → konstantin.tkachenko.wildix (on 2024-09-30) provenance

This version was published by a different npm account than previous versions on 2024-09-30. 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.0.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: vruban.wildix → sergey.dartchuk (on 2024-08-22, known maintainer) provenance

This version was published by a different npm account (sergey.dartchuk) than the most recent previously approved version (vruban.wildix) on 2024-08-22, 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.0.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: vruban.wildix → vladimir.gorobets.wildix (on 2024-05-08, 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-05-08, 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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.8

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

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

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

This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (vruban.wildix) on 2024-02-22. It has since remained available on npm for 884 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.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.