@wildix/wim-voicebots-client
@wildix/wim-voicebots-client client
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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:@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 | |
| 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/middleware-host-header | 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 |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 4.0.7 | 8 / 6 | |
| 4.0.4 | 8 / 6 | |
| 4.0.3 | 8 / 6 | |
| 4.0.2 | 8 / 6 | |
| 4.0.1 | 8 / 6 | |
| 3.1.10 | 8 / 6 | |
| 1.1.9 | 34 / 6 | |
| 1.1.8 | 34 / 6 | |
| 1.1.7 | 34 / 6 | |
| 1.1.6 | 34 / 6 | |
| 1.1.5 | 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 | 34 / 6 | |
| 1.0.27 | 34 / 6 | |
| 1.0.26 | 34 / 6 | |
| 1.0.25 | 34 / 6 | |
| 1.0.24 | 34 / 6 | |
| 1.0.23 | 34 / 6 | |
| 1.0.22 | 30 / 6 | |
| 1.0.21 | 30 / 6 | |
| 1.0.20 | 30 / 6 | |
| 1.0.19 | 30 / 6 | |
| 1.0.18 | 30 / 6 | |
| 1.0.17 | 30 / 6 | |
| 1.0.16 | 30 / 6 | |
| 1.0.15 | 30 / 6 | |
| 1.0.14 | 30 / 6 | |
| 1.0.13 | 30 / 6 | |
| 1.0.12 | 30 / 6 | |
| 1.0.11 | 30 / 6 | |
| 1.0.10 | 30 / 6 | |
| 1.0.9 | 30 / 6 | |
| 1.0.8 | 30 / 6 | |
| 1.0.7 | 30 / 6 | |
| 1.0.6 | 30 / 6 | |
| 1.0.5 | 30 / 6 | |
| 1.0.4 | 30 / 6 | |
| 1.0.3 | 30 / 6 | |
| 1.0.2 | 30 / 6 | |
| 1.0.1 | 30 / 6 |
v4.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (konstantin.tkachenko.wildix) than the most recent previously approved version (vruban.wildix) on 2026-07-24, but konstantin.tkachenko.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.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vruban.wildix) than the most recent previously approved version (vladimir.gorobets.wildix) 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.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vladimir.gorobets.wildix) than the most recent previously approved version (alex.pokidin) 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.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alex.pokidin) than the most recent previously approved version (vruban.wildix) on 2026-07-14, but alex.pokidin 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.