@cloudbase/container
cloudbase javascript sdk functions componets
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): Active monorepo with frequent coordinated releases; rapid publish is expected for this package family. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is used in a WASM interop bridge for property access; not obfuscation, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@cloudbase/adapter-interface | AI (phantom-deps): Same-org sibling dep; declared but may be used transitively or via type-only imports. | ai |
Versions (showing 80 of 80)
| Version | Deps | Published |
|---|---|---|
| 3.3.13 | 2 / 3 | |
| 3.3.12 | 2 / 3 | |
| 3.3.11 | 2 / 3 | |
| 3.3.10 | 2 / 3 | |
| 3.3.9 | 2 / 3 | |
| 3.3.8 | 2 / 3 | |
| 3.3.7 | 2 / 3 | |
| 3.3.6 | 2 / 3 | |
| 3.3.5 | 2 / 3 | |
| 3.3.3 | 2 / 3 | |
| 3.3.2 | 2 / 3 | |
| 3.3.0 | 2 / 3 | |
| 3.2.2 | 2 / 3 | |
| 3.2.0 | 2 / 3 | |
| 3.1.9 | 2 / 3 | |
| 3.1.6 | 2 / 3 | |
| 3.1.5 | 2 / 3 | |
| 3.1.4 | 2 / 3 | |
| 3.1.3 | 2 / 3 | |
| 3.1.0 | 2 / 3 | |
| 3.0.5 | 2 / 3 | |
| 3.0.3 | 2 / 3 | |
| 2.28.8 | 2 / 3 | |
| 2.28.6 | 2 / 3 | |
| 2.28.5 | 2 / 3 | |
| 2.28.4 | 2 / 3 | |
| 2.28.3 | 2 / 3 | |
| 2.28.2 | 2 / 3 | |
| 2.28.1 | 2 / 3 | |
| 2.28.0 | 2 / 3 | |
| 2.26.3 | 2 / 3 | |
| 2.26.2 | 2 / 3 | |
| 2.26.1 | 2 / 3 | |
| 2.26.0 | 2 / 3 | |
| 2.25.9 | 2 / 3 | |
| 2.24.9 | 2 / 3 | |
| 2.24.8 | 2 / 3 | |
| 2.24.6 | 2 / 3 | |
| 2.24.5 | 2 / 3 | |
| 2.24.4 | 2 / 3 | |
| 2.23.3 | 2 / 3 | |
| 2.23.1 | 2 / 3 | |
| 2.22.10 | 2 / 3 | |
| 2.22.8 | 2 / 3 | |
| 2.22.7 | 2 / 3 | |
| 2.22.6 | 2 / 3 | |
| 2.22.4 | 2 / 3 | |
| 2.22.0 | 2 / 3 | |
| 2.21.7 | 2 / 3 | |
| 2.20.13 | 2 / 3 | |
| 2.20.10 | 2 / 3 | |
| 2.20.7 | 2 / 3 | |
| 2.20.4 | 2 / 3 | |
| 2.20.2 | 2 / 3 | |
| 2.19.7 | 2 / 3 | |
| 2.19.3 | 2 / 3 | |
| 2.19.2 | 2 / 3 | |
| 2.18.2 | 2 / 3 | |
| 2.18.0 | 2 / 3 | |
| 2.17.12 | 2 / 3 | |
| 2.17.1 | 2 / 3 | |
| 2.15.1 | 2 / 3 | |
| 2.14.0 | 2 / 3 | |
| 2.13.0 | 2 / 3 | |
| 2.12.1 | 2 / 3 | |
| 2.12.0 | 2 / 3 | |
| 2.11.0 | 2 / 3 | |
| 2.10.0 | 2 / 3 | |
| 2.9.8 | 2 / 3 | |
| 2.9.7 | 2 / 3 | |
| 2.9.6 | 2 / 3 | |
| 2.9.3 | 2 / 3 | |
| 2.9.2 | 2 / 3 | |
| 2.9.1 | 2 / 3 | |
| 2.9.0 | 2 / 3 | |
| 2.8.35 | 2 / 3 | |
| 2.8.34 | 2 / 3 | |
| 2.8.33 | 2 / 3 | |
| 2.8.32 | 2 / 3 | |
| 2.8.31 | 2 / 3 |
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.