@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, 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher has strong track record (108 approved, 0 rejected); likely org member rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Multiple wildix.com-affiliated maintainers added, consistent with internal org monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Established @wildix org package; no provenance attestation is consistent across all versions. | 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:@smithy/invalid-dependency | AI (phantom-deps): Smithy 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-recursion-detection | 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:@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 |
Versions (showing 51 of 68)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 8 / 6 | |
| 4.0.2 | 8 / 6 | |
| 4.0.1 | 8 / 6 | |
| 3.1.29 | 8 / 6 | |
| 1.2.29 | 34 / 6 | |
| 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.2.1 | 34 / 6 | |
| 1.2.0 | 34 / 6 | |
| 1.1.1 | 34 / 6 | |
| 1.1.0 | 34 / 6 | |
| 1.0.39 | 34 / 6 | |
| 1.0.38 | 34 / 6 | |
| 1.0.37 | 34 / 6 | |
| 1.0.36 | 34 / 6 | |
| 1.0.35 | 34 / 6 | |
| 1.0.34 | 34 / 6 | |
| 1.0.33 | 34 / 6 | |
| 1.0.32 | 34 / 6 | |
| 1.0.31 | 34 / 6 | |
| 1.0.30 | 34 / 6 | |
| 1.0.29 | 30 / 6 | |
| 1.0.28 | 30 / 6 | |
| 1.0.27 | 30 / 6 | |
| 1.0.26 | 30 / 6 | |
| 1.0.25 | 30 / 6 | |
| 1.0.24 | 30 / 6 | |
| 1.0.23 | 30 / 6 | |
| 1.0.22 | 30 / 6 | |
| 1.0.21 | 30 / 6 | |
| 1.0.20 | 30 / 6 | |
| 1.0.19 | 30 / 6 |
v4.0.3
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 (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.2
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 (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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.29
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-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.30
2 findingsThis version was published by a different npm account than previous versions on 2025-04-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
2 findingsThis version was published by a different npm account than previous versions on 2025-03-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
2 findingsThis version was published by a different npm account than previous versions on 2025-03-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
2 findingsThis version was published by a different npm account than previous versions on 2025-03-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
2 findingsThis version was published by a different npm account than previous versions on 2025-03-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
2 findingsThis version was published by a different npm account than previous versions on 2025-03-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
2 findingsThis version was published by a different npm account than previous versions on 2025-03-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
2 findingsThis version was published by a different npm account than previous versions on 2025-02-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
2 findingsThis version was published by a different npm account than previous versions on 2025-01-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
2 findingsThis version was published by a different npm account than previous versions on 2025-01-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
2 findingsThis version was published by a different npm account than previous versions on 2025-01-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
2 findingsThis version was published by a different npm account than previous versions on 2024-12-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.