@cloudbase/wx-cloud-client-sdk
wx cloud client sdk
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @cloudbase org package; lack of provenance is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:core-js-pure | AI (phantom-deps): Bundled SDK; core-js-pure is a build-time polyfill dependency, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@cloudbase/adapter-wx_mp | AI (phantom-deps): Same-org adapter; used indirectly via bundling, stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.8.8 | 2 / 21 | |
| 1.8.7 | 2 / 21 | |
| 1.8.5 | 3 / 21 | |
| 1.8.4 | 3 / 21 | |
| 1.8.3 | 2 / 21 | |
| 1.8.2 | 2 / 21 | |
| 1.8.1 | 2 / 21 | |
| 1.8.0 | 2 / 21 | |
| 1.7.2 | 1 / 16 | |
| 1.7.1 | 1 / 16 | |
| 1.6.1 | 0 / 16 | |
| 1.6.0 | 0 / 16 |
v1.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.