@wildix/wda-history-client
@wildix/wda-history-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @wildix org package; no provenance attestation is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@smithy/config-resolver | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS client. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS client. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-logger | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-host-header | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-recursion-detection | AI (phantom-deps): AWS SDK framework-scoped package; loaded by convention in AWS client. | ai | |
| phantom-deps | phantom-dep:@smithy/invalid-dependency | AI (phantom-deps): Smithy framework-scoped package; loaded by convention in AWS client. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.2.28 | 34 / 6 | |
| 1.2.27 | 34 / 6 | |
| 1.2.26 | 34 / 6 | |
| 1.2.25 | 34 / 6 | |
| 1.2.24 | 34 / 6 | |
| 1.2.22 | 34 / 6 | |
| 1.2.21 | 34 / 6 | |
| 1.2.20 | 34 / 6 | |
| 1.2.19 | 34 / 6 | |
| 1.2.18 | 34 / 6 | |
| 1.2.17 | 34 / 6 | |
| 1.2.16 | 34 / 6 | |
| 1.2.15 | 34 / 6 | |
| 1.2.14 | 34 / 6 | |
| 1.2.13 | 34 / 6 | |
| 1.2.12 | 34 / 6 | |
| 1.2.11 | 34 / 6 | |
| 1.2.10 | 34 / 6 | |
| 1.2.9 | 34 / 6 | |
| 1.2.8 | 34 / 6 | |
| 1.2.7 | 34 / 6 | |
| 1.0.37 | 34 / 6 | |
| 1.0.34 | 34 / 6 | |
| 1.0.32 | 34 / 6 | |
| 1.0.31 | 34 / 6 |
v1.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gennadiy.ganchev) than the most recent previously approved version (vruban.wildix) on 2026-06-02, but gennadiy.ganchev 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.2.24
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gennadiy.ganchev) than the most recent previously approved version (vruban.wildix) on 2026-06-02, but gennadiy.ganchev 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.2.22
2 findings[Accepted risk] Package 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 (gennadiy.ganchev) on 2026-06-01, 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.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
2 findingsThis version was published by a different npm account than previous versions on 2025-07-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.