@cloudbase/functions
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): Monorepo SDK with 321 versions; rapid successive publishes are consistent with automated coordinated releases across sibling packages. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is consistent across all 311 versions and is not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@cloudbase/adapter-interface | AI (phantom-deps): Same-org sibling dep; declared as transitive peer, not directly imported — stable false positive for this package. | ai |
Versions (showing 100 of 149)
| Version | Deps | Published |
|---|---|---|
| 3.3.13 | 4 / 0 | |
| 3.3.12 | 4 / 0 | |
| 3.3.11 | 4 / 0 | |
| 3.3.10 | 4 / 0 | |
| 3.3.9 | 4 / 0 | |
| 3.3.8 | 4 / 0 | |
| 3.3.7 | 4 / 0 | |
| 3.3.6 | 4 / 0 | |
| 3.3.5 | 4 / 0 | |
| 3.3.4 | 4 / 0 | |
| 3.3.3 | 4 / 0 | |
| 3.3.2 | 4 / 0 | |
| 3.3.1 | 4 / 0 | |
| 3.3.0 | 4 / 0 | |
| 3.2.2 | 4 / 0 | |
| 3.1.2 | 4 / 0 | |
| 3.1.1 | 4 / 0 | |
| 3.1.0 | 4 / 0 | |
| 3.0.6 | 4 / 0 | |
| 3.0.5 | 4 / 0 | |
| 3.0.4 | 4 / 0 | |
| 3.0.3 | 4 / 0 | |
| 3.0.2 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 2.28.8 | 4 / 0 | |
| 2.28.6 | 4 / 0 | |
| 2.28.5 | 4 / 0 | |
| 2.28.4 | 4 / 0 | |
| 2.28.3 | 4 / 0 | |
| 2.28.2 | 4 / 0 | |
| 2.28.1 | 4 / 0 | |
| 2.28.0 | 4 / 0 | |
| 2.27.5 | 4 / 0 | |
| 2.27.4 | 4 / 0 | |
| 2.27.3 | 4 / 0 | |
| 2.27.2 | 4 / 0 | |
| 2.25.10 | 4 / 0 | |
| 2.25.9 | 4 / 0 | |
| 2.25.8 | 4 / 0 | |
| 2.25.7 | 4 / 0 | |
| 2.25.6 | 4 / 0 | |
| 2.25.5 | 4 / 0 | |
| 2.25.4 | 4 / 0 | |
| 2.25.3 | 4 / 0 | |
| 2.25.2 | 4 / 0 | |
| 2.25.1 | 4 / 0 | |
| 2.25.0 | 4 / 0 | |
| 2.24.10 | 4 / 0 | |
| 2.24.9 | 4 / 0 | |
| 2.24.8 | 4 / 0 | |
| 2.24.7 | 4 / 0 | |
| 2.24.6 | 4 / 0 | |
| 2.24.5 | 4 / 0 | |
| 2.24.4 | 4 / 0 | |
| 2.24.3 | 4 / 0 | |
| 2.24.2 | 4 / 0 | |
| 2.24.1 | 4 / 0 | |
| 2.24.0 | 4 / 0 | |
| 2.23.3 | 4 / 0 | |
| 2.23.2 | 4 / 0 | |
| 2.23.1 | 4 / 0 | |
| 2.23.0 | 4 / 0 | |
| 2.22.10 | 4 / 0 | |
| 2.22.9 | 4 / 0 | |
| 2.22.8 | 4 / 0 | |
| 2.22.7 | 4 / 0 | |
| 2.22.6 | 4 / 0 | |
| 2.22.5 | 4 / 0 | |
| 2.22.4 | 4 / 0 | |
| 2.22.2 | 4 / 0 | |
| 2.22.1 | 4 / 0 | |
| 2.22.0 | 4 / 0 | |
| 2.21.10 | 4 / 0 | |
| 2.21.9 | 4 / 0 | |
| 2.21.8 | 4 / 0 | |
| 2.21.7 | 4 / 0 | |
| 2.21.6 | 4 / 0 | |
| 2.21.5 | 4 / 0 | |
| 2.21.4 | 4 / 0 | |
| 2.21.3 | 4 / 0 | |
| 2.21.2 | 4 / 0 | |
| 2.21.1 | 4 / 0 | |
| 2.21.0 | 4 / 0 | |
| 2.20.14 | 4 / 0 | |
| 2.20.13 | 4 / 0 | |
| 2.20.12 | 4 / 0 | |
| 2.20.11 | 4 / 0 | |
| 2.20.10 | 4 / 0 | |
| 2.20.9 | 4 / 0 | |
| 2.20.8 | 4 / 0 | |
| 2.20.7 | 4 / 0 | |
| 2.20.6 | 4 / 0 | |
| 2.20.4 | 4 / 0 | |
| 2.20.3 | 4 / 0 | |
| 2.20.2 | 4 / 0 | |
| 2.20.1 | 4 / 0 | |
| 2.20.0 | 4 / 0 | |
| 2.19.7 | 4 / 0 | |
| 2.19.6 | 4 / 0 | |
| 2.19.5 | 4 / 0 |
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.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.
v2.21.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.