@wildix/wms-api-client
@wildix/wms-api-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): AWS SDK framework-scoped packages loaded by convention in AWS client. | ai | |
| phantom-deps | phantom-dep:@smithy/config-resolver | AI (phantom-deps): Smithy framework-scoped package; stable pattern for AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/middleware-stack | AI (phantom-deps): Smithy framework-scoped package; stable pattern for AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-logger | AI (phantom-deps): AWS SDK framework-scoped package; stable pattern for AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@smithy/invalid-dependency | AI (phantom-deps): Smithy framework-scoped package; stable pattern for AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-host-header | AI (phantom-deps): AWS SDK framework-scoped package; stable pattern for AWS SDK clients. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/middleware-recursion-detection | AI (phantom-deps): AWS SDK framework-scoped package; stable pattern for AWS SDK clients. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 34 / 6 | |
| 1.2.2 | 34 / 6 | |
| 1.2.1 | 34 / 6 | |
| 1.2.0 | 34 / 6 | |
| 1.1.27 | 34 / 6 | |
| 1.1.26 | 34 / 6 | |
| 1.1.24 | 34 / 6 | |
| 1.1.23 | 34 / 6 | |
| 1.1.22 | 34 / 6 | |
| 1.1.21 | 34 / 6 | |
| 1.1.20 | 34 / 6 |
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.