@cloudbase/js-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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): High-frequency org SDK with 361 versions; rapid successive publishes are normal for this package. | ai | |
| dependencies | unvetted-dep:@cloudbase/database | AI (dependencies): Internal @cloudbase org dependency; consistent with this SDK's architecture across versions. | ai | |
| dependencies | unvetted-dep:@cloudbase/adapter-interface | AI (dependencies): Internal @cloudbase org dependency; stable pattern across this package's release history. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in minified SDK bundle is expected for encoding/decoding data, not payload hiding. | ai | |
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): @cloudbase/js-sdk is the official Tencent CloudBase SDK, not a typosquat of aws-sdk. | ai | |
| phantom-deps | phantom-dep:@cloudbase/utilities | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo sub-packages. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode in minified SDK bundle is a standard utility pattern, not malicious. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires in minified bundle output; standard pattern in bundled SDK code, not malicious. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get in minified bundle is a normal transpilation artifact, not evasion. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 3.3.12 | 15 / 0 | |
| 3.3.11 | 15 / 0 | |
| 3.3.10 | 15 / 0 | |
| 3.3.9 | 15 / 0 | |
| 3.3.8 | 15 / 0 | |
| 3.3.7 | 15 / 0 | |
| 3.3.6 | 15 / 0 | |
| 3.3.5 | 15 / 0 | |
| 3.3.4 | 15 / 0 | |
| 3.3.3 | 15 / 0 | |
| 3.3.2 | 15 / 0 | |
| 3.3.1 | 15 / 0 | |
| 3.3.0 | 15 / 0 | |
| 2.28.8 | 15 / 0 | |
| 2.28.6 | 15 / 0 | |
| 2.28.5 | 15 / 0 | |
| 2.28.4 | 15 / 0 | |
| 2.28.3 | 15 / 0 | |
| 2.28.2 | 15 / 0 | |
| 2.28.1 | 15 / 0 | |
| 2.28.0 | 15 / 0 | |
| 2.27.5 | 15 / 0 | |
| 2.27.4 | 15 / 0 | |
| 2.27.3 | 15 / 0 | |
| 2.22.10 | 14 / 0 | |
| 2.22.9 | 14 / 0 | |
| 2.22.8 | 14 / 0 | |
| 2.22.7 | 14 / 0 | |
| 2.22.6 | 14 / 0 | |
| 2.22.5 | 14 / 0 | |
| 2.22.4 | 14 / 0 | |
| 2.21.10 | 13 / 0 | |
| 2.21.9 | 13 / 0 | |
| 2.21.8 | 13 / 0 | |
| 2.21.7 | 13 / 0 | |
| 2.21.6 | 13 / 0 | |
| 2.21.5 | 13 / 0 | |
| 2.21.4 | 13 / 0 | |
| 2.21.3 | 13 / 0 | |
| 2.21.2 | 13 / 0 | |
| 2.21.1 | 13 / 0 | |
| 2.21.0 | 13 / 0 | |
| 2.20.14 | 13 / 0 | |
| 2.20.13 | 13 / 0 | |
| 2.20.12 | 13 / 0 | |
| 2.20.10 | 13 / 0 | |
| 2.20.9 | 13 / 0 | |
| 2.20.8 | 13 / 0 | |
| 2.20.7 | 13 / 0 | |
| 2.20.6 | 13 / 0 | |
| 2.20.4 | 13 / 0 |
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.