@cubejs-backend/bigquery-driver
Cube.js BigQuery 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Monorepo package; provenance adoption is sparse across npm ecosystem. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish; established Cube.js org package with 789 prior versions. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/dotenv | AI (dependencies): Same org-scoped package (@cubejs-backend); internal dependency within the Cube.js monorepo, stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Cube.js monorepo driver; README and metadata patterns are false positives for this well-known OSS project. | ai | |
| phantom-deps | phantom-dep:@cubejs-backend/dotenv | AI (phantom-deps): Same-org scoped dependency in a monorepo; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 100 of 214)
| Version | Deps | Published |
|---|---|---|
| 1.3.65 | 6 / 7 | |
| 1.3.64 | 6 / 7 | |
| 1.3.62 | 6 / 7 | |
| 1.3.61 | 6 / 7 | |
| 1.3.60 | 6 / 7 | |
| 1.3.59 | 6 / 7 | |
| 1.3.56 | 6 / 7 | |
| 1.3.55 | 6 / 7 | |
| 1.3.54 | 6 / 7 | |
| 1.3.52 | 6 / 7 | |
| 1.3.51 | 6 / 7 | |
| 1.3.50 | 6 / 7 | |
| 1.3.49 | 6 / 7 | |
| 1.3.48 | 6 / 7 | |
| 1.3.47 | 6 / 7 | |
| 1.3.45 | 6 / 7 | |
| 1.3.44 | 6 / 7 | |
| 1.3.42 | 6 / 7 | |
| 1.3.41 | 6 / 7 | |
| 1.3.39 | 6 / 7 | |
| 1.3.38 | 6 / 7 | |
| 1.3.36 | 6 / 7 | |
| 1.3.34 | 6 / 7 | |
| 1.3.33 | 6 / 7 | |
| 1.3.32 | 6 / 7 | |
| 1.3.30 | 6 / 7 | |
| 1.3.29 | 6 / 7 | |
| 1.3.27 | 6 / 7 | |
| 1.3.25 | 6 / 7 | |
| 1.3.24 | 6 / 7 | |
| 1.3.22 | 6 / 7 | |
| 1.3.21 | 6 / 7 | |
| 1.3.19 | 6 / 7 | |
| 1.3.18 | 6 / 7 | |
| 1.3.17 | 6 / 7 | |
| 1.3.16 | 6 / 7 | |
| 1.3.12 | 6 / 7 | |
| 1.3.11 | 6 / 7 | |
| 1.3.10 | 6 / 7 | |
| 1.3.9 | 6 / 7 | |
| 1.3.8 | 6 / 7 | |
| 1.3.7 | 6 / 7 | |
| 1.3.6 | 6 / 7 | |
| 1.3.5 | 6 / 7 | |
| 1.3.4 | 6 / 7 | |
| 1.3.3 | 6 / 7 | |
| 1.3.2 | 6 / 7 | |
| 1.3.1 | 6 / 7 | |
| 1.3.0 | 6 / 7 | |
| 1.2.34 | 6 / 7 | |
| 1.2.33 | 6 / 7 | |
| 1.2.32 | 6 / 7 | |
| 1.2.31 | 6 / 7 | |
| 1.2.30 | 6 / 7 | |
| 1.2.29 | 6 / 7 | |
| 1.2.28 | 6 / 7 | |
| 1.2.27 | 6 / 7 | |
| 1.2.26 | 6 / 7 | |
| 1.2.25 | 6 / 7 | |
| 1.2.24 | 6 / 7 | |
| 1.2.23 | 6 / 7 | |
| 1.2.22 | 6 / 7 | |
| 1.2.21 | 6 / 7 | |
| 1.2.20 | 6 / 7 | |
| 1.2.19 | 6 / 7 | |
| 1.2.18 | 6 / 7 | |
| 1.2.17 | 6 / 7 | |
| 1.2.16 | 6 / 7 | |
| 1.2.15 | 6 / 7 | |
| 1.2.14 | 6 / 7 | |
| 1.2.13 | 6 / 7 | |
| 1.2.12 | 6 / 7 | |
| 1.2.11 | 6 / 7 | |
| 1.2.10 | 6 / 7 | |
| 1.2.9 | 6 / 7 | |
| 1.2.8 | 6 / 7 | |
| 1.2.7 | 6 / 7 | |
| 1.2.6 | 6 / 7 | |
| 1.2.5 | 6 / 7 | |
| 1.2.4 | 6 / 7 | |
| 1.2.3 | 6 / 7 | |
| 1.2.2 | 6 / 7 | |
| 1.2.1 | 6 / 7 | |
| 1.2.0 | 6 / 7 | |
| 1.1.17 | 6 / 7 | |
| 1.1.16 | 6 / 7 | |
| 1.1.15 | 6 / 7 | |
| 1.1.14 | 6 / 7 | |
| 1.1.13 | 6 / 7 | |
| 1.1.12 | 6 / 7 | |
| 1.1.11 | 6 / 7 | |
| 1.1.10 | 6 / 7 | |
| 1.1.9 | 6 / 7 | |
| 1.1.8 | 6 / 7 | |
| 1.1.7 | 6 / 7 | |
| 1.1.6 | 6 / 7 | |
| 1.1.5 | 6 / 7 | |
| 1.1.4 | 6 / 7 | |
| 1.1.3 | 6 / 7 | |
| 1.1.2 | 6 / 7 |
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.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.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.