@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 — 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 |
|---|---|---|---|---|
| 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 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 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.3 | 1 / 0 | |
| 3.3.2 | 1 / 0 | |
| 3.2.2 | 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 |
v3.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.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.
v3.3.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.
v3.2.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.
v2.28.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.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.
v2.27.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.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.
v2.27.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.