@cubejs-backend/firebolt-driver
Cube.js Firebolt database driver
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Cube.js monorepo with SLSA provenance; automated CI/CD publisher consistent with legitimate release cadence resumption. | ai | |
| dependencies | unvetted-dep:firebolt-sdk | AI (dependencies): firebolt-sdk is the official Firebolt database SDK; expected dependency for this driver package. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all cubejs-backend packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo driver package; README and metadata patterns are typical for this ecosystem, not spam. | ai |
Versions (showing 27 of 129)
| Version | Deps | Published |
|---|---|---|
| 1.3.37 | 4 / 3 | |
| 1.3.36 | 4 / 3 | |
| 1.3.35 | 4 / 3 | |
| 1.3.34 | 4 / 3 | |
| 1.3.33 | 4 / 3 | |
| 1.3.32 | 4 / 3 | |
| 1.3.31 | 4 / 3 | |
| 1.3.30 | 4 / 3 | |
| 1.3.29 | 4 / 3 | |
| 1.3.28 | 4 / 3 | |
| 1.3.27 | 4 / 3 | |
| 1.3.26 | 4 / 3 | |
| 1.3.25 | 4 / 3 | |
| 1.3.24 | 4 / 3 | |
| 1.3.23 | 4 / 3 | |
| 1.3.22 | 4 / 3 | |
| 1.3.21 | 4 / 3 | |
| 1.3.20 | 4 / 3 | |
| 1.3.19 | 4 / 3 | |
| 1.3.18 | 4 / 3 | |
| 1.3.17 | 4 / 3 | |
| 1.3.16 | 4 / 3 | |
| 1.3.15 | 4 / 3 | |
| 1.3.14 | 4 / 3 | |
| 1.3.13 | 4 / 3 | |
| 1.3.12 | 4 / 3 | |
| 1.3.11 | 4 / 3 |
v1.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.