@cloudbase/types
cloudbase javascript sdk types
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-cadence automated releases are normal for this monorepo-style SDK package with 305 versions in registry. | ai | |
| dependencies | unvetted-dep:@cloudbase/adapter-interface | AI (dependencies): Sibling package in the same TencentCloudBase org; stable long-term dependency across many versions. | ai | |
| provenance | no-provenance | AI (provenance): Long-established Tencent CloudBase org package; lack of provenance is consistent across all 295 versions. | ai |
Versions (showing 100 of 171)
| Version | Deps | Published |
|---|---|---|
| 3.6.2 | 1 / 0 | |
| 3.3.13 | 1 / 0 | |
| 3.3.12 | 1 / 0 | |
| 3.3.11 | 1 / 0 | |
| 3.3.10 | 1 / 0 | |
| 3.3.9 | 1 / 0 | |
| 3.3.8 | 1 / 0 | |
| 3.3.7 | 1 / 0 | |
| 3.3.6 | 1 / 0 | |
| 3.3.5 | 1 / 0 | |
| 3.3.4 | 1 / 0 | |
| 3.3.3 | 1 / 0 | |
| 3.3.2 | 1 / 0 | |
| 3.3.1 | 1 / 0 | |
| 3.3.0 | 1 / 0 | |
| 3.2.2 | 1 / 0 | |
| 3.2.1 | 1 / 0 | |
| 3.2.0 | 1 / 0 | |
| 3.1.12 | 1 / 0 | |
| 3.1.11 | 1 / 0 | |
| 3.1.10 | 1 / 0 | |
| 3.1.9 | 1 / 0 | |
| 3.1.8 | 1 / 0 | |
| 3.1.7 | 1 / 0 | |
| 3.1.6 | 1 / 0 | |
| 3.1.5 | 1 / 0 | |
| 3.1.4 | 1 / 0 | |
| 3.1.3 | 1 / 0 | |
| 3.1.2 | 1 / 0 | |
| 3.1.1 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 3.0.6 | 1 / 0 | |
| 3.0.5 | 1 / 0 | |
| 3.0.4 | 1 / 0 | |
| 3.0.3 | 1 / 0 | |
| 3.0.2 | 1 / 0 | |
| 3.0.1 | 1 / 0 | |
| 2.30.0 | 1 / 0 | |
| 2.28.8 | 1 / 0 | |
| 2.28.6 | 1 / 0 | |
| 2.28.5 | 1 / 0 | |
| 2.28.4 | 1 / 0 | |
| 2.28.3 | 1 / 0 | |
| 2.28.2 | 1 / 0 | |
| 2.28.1 | 1 / 0 | |
| 2.28.0 | 1 / 0 | |
| 2.27.5 | 1 / 0 | |
| 2.27.4 | 1 / 0 | |
| 2.27.3 | 1 / 0 | |
| 2.27.2 | 1 / 0 | |
| 2.27.1 | 1 / 0 | |
| 2.27.0 | 1 / 0 | |
| 2.26.3 | 1 / 0 | |
| 2.26.2 | 1 / 0 | |
| 2.26.1 | 1 / 0 | |
| 2.26.0 | 1 / 0 | |
| 2.25.11 | 1 / 0 | |
| 2.25.10 | 1 / 0 | |
| 2.25.9 | 1 / 0 | |
| 2.25.8 | 1 / 0 | |
| 2.25.7 | 1 / 0 | |
| 2.25.6 | 1 / 0 | |
| 2.25.5 | 1 / 0 | |
| 2.25.4 | 1 / 0 | |
| 2.25.3 | 1 / 0 | |
| 2.25.2 | 1 / 0 | |
| 2.25.1 | 1 / 0 | |
| 2.25.0 | 1 / 0 | |
| 2.24.10 | 1 / 0 | |
| 2.24.9 | 1 / 0 | |
| 2.24.8 | 1 / 0 | |
| 2.24.7 | 1 / 0 | |
| 2.24.6 | 1 / 0 | |
| 2.24.5 | 1 / 0 | |
| 2.24.4 | 1 / 0 | |
| 2.24.3 | 1 / 0 | |
| 2.24.2 | 1 / 0 | |
| 2.24.1 | 1 / 0 | |
| 2.24.0 | 1 / 0 | |
| 2.23.3 | 1 / 0 | |
| 2.23.2 | 1 / 0 | |
| 2.23.1 | 1 / 0 | |
| 2.23.0 | 1 / 0 | |
| 2.22.10 | 1 / 0 | |
| 2.22.9 | 1 / 0 | |
| 2.22.8 | 1 / 0 | |
| 2.22.7 | 1 / 0 | |
| 2.22.6 | 1 / 0 | |
| 2.22.5 | 1 / 0 | |
| 2.22.4 | 1 / 0 | |
| 2.22.3 | 1 / 0 | |
| 2.22.2 | 1 / 0 | |
| 2.22.1 | 1 / 0 | |
| 2.22.0 | 1 / 0 | |
| 2.21.10 | 1 / 0 | |
| 2.21.9 | 1 / 0 | |
| 2.21.8 | 1 / 0 | |
| 2.21.7 | 1 / 0 | |
| 2.21.6 | 1 / 0 | |
| 2.21.5 | 1 / 0 |
v3.6.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 (yhyang) than the most recent previously approved version (yuzhen) on 2026-07-02, but yhyang 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.
v3.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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 (yuzhen) than the most recent previously approved version (binggg) on 2026-03-10, 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.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.11
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 (binggg) on 2026-03-11, 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.
v2.25.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.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 (woodenstone) on 2025-12-17, 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.
v2.23.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 (binggg) than the most recent previously approved version (woodenstone) on 2025-12-12, 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.
v2.22.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.