@cloudbase/ai
cloudbase js sdk ai module
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/miniprogram/index.js | AI (source-diff): Network calls and dynamic module loading are inherent to the CloudBase SDK; no dropper behavior visible in the bundle. | ai | |
| source-diff | obfuscated-file:dist/miniprogram/index.js | AI (source-diff): Standard webpack UMD bundle for miniprogram target; minification is expected and documented in build scripts. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): High-frequency automated releases are normal for this monorepo SDK; 229 versions published over 644 days confirms the pattern. | ai | |
| dependencies | unvetted-dep:text-encoding-shim | AI (dependencies): text-encoding-shim is a standard TextEncoder/TextDecoder polyfill; appropriate for a cross-env SDK. | ai | |
| dependencies | unvetted-dep:@mattiasbuelens/web-streams-adapter | AI (dependencies): Known web-streams adapter shim used in cross-environment streaming; no malicious history. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @cloudbase/ai package; Levenshtein match to 'hapi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @cloudbase/ai package; Levenshtein match to 'pg' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @cloudbase/ai package; Levenshtein match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @cloudbase/ai package; Levenshtein match to 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @cloudbase/ai package; Levenshtein match to 'ajv' is a false positive. | ai |
Versions (showing 51 of 88)
| Version | Deps | Published |
|---|---|---|
| 3.3.13 | 5 / 1 | |
| 3.3.12 | 5 / 1 | |
| 3.3.11 | 5 / 1 | |
| 3.3.10 | 5 / 1 | |
| 3.3.9 | 5 / 1 | |
| 3.3.8 | 5 / 1 | |
| 3.3.7 | 5 / 1 | |
| 3.3.6 | 5 / 1 | |
| 3.3.5 | 5 / 1 | |
| 3.3.4 | 5 / 1 | |
| 3.3.3 | 5 / 1 | |
| 3.3.2 | 5 / 1 | |
| 3.3.1 | 5 / 1 | |
| 3.3.0 | 5 / 1 | |
| 3.2.2 | 5 / 1 | |
| 2.28.8 | 5 / 1 | |
| 2.28.6 | 5 / 1 | |
| 2.28.5 | 5 / 1 | |
| 2.28.4 | 5 / 1 | |
| 2.28.3 | 5 / 1 | |
| 2.28.2 | 5 / 1 | |
| 2.28.1 | 5 / 1 | |
| 2.28.0 | 5 / 1 | |
| 2.27.5 | 5 / 1 | |
| 2.27.4 | 5 / 1 | |
| 2.27.3 | 5 / 1 | |
| 2.27.2 | 5 / 1 | |
| 2.22.10 | 5 / 1 | |
| 2.22.9 | 5 / 1 | |
| 2.22.8 | 5 / 1 | |
| 2.22.7 | 5 / 1 | |
| 2.22.6 | 5 / 1 | |
| 2.22.5 | 5 / 1 | |
| 2.22.4 | 5 / 1 | |
| 2.22.3 | 5 / 1 | |
| 2.22.2 | 5 / 1 | |
| 2.22.1 | 5 / 1 | |
| 2.22.0 | 5 / 1 | |
| 2.21.10 | 5 / 1 | |
| 2.21.9 | 5 / 1 | |
| 2.21.8 | 5 / 1 | |
| 2.21.7 | 5 / 1 | |
| 2.21.6 | 5 / 1 | |
| 2.21.5 | 5 / 1 | |
| 2.21.4 | 5 / 1 | |
| 2.21.3 | 5 / 1 | |
| 2.21.2 | 5 / 1 | |
| 2.21.1 | 5 / 1 | |
| 2.21.0 | 5 / 1 | |
| 2.20.14 | 5 / 1 | |
| 2.20.13 | 5 / 1 |
v3.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.
v3.2.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.