@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, so a manually published version cannot be tied back to a reviewed commit.
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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.8.10 | 2 / 21 | |
| 1.8.9 | 2 / 21 | |
| 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 | |
| 1.5.0 | 0 / 16 | |
| 1.4.0 | 0 / 16 | |
| 1.3.1 | 0 / 16 | |
| 1.3.0 | 0 / 16 | |
| 1.2.1 | 0 / 13 | |
| 1.2.0 | 0 / 13 | |
| 1.1.0 | 0 / 10 | |
| 1.0.0 | 0 / 9 |
v1.8.10
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 (wedabot) than the most recent previously approved version (yuzhen) on 2026-07-17, but wedabot 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.8.9
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 (yuzhen) than the most recent previously approved version (yhyang) on 2026-07-02, but yuzhen 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.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
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 (wedabot) than the most recent previously approved version (binggg) on 2024-11-07, but wedabot 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.3.0
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 (wedabot) than the most recent previously approved version (binggg) on 2024-10-23, but wedabot 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.1
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 (binggg) than the most recent previously approved version (wedabot) on 2024-08-08, but binggg 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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.0.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.