@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 14 of 215)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 6 / 7 | |
| 1.1.0 | 6 / 7 | |
| 1.0.12 | 6 / 7 | |
| 1.0.11 | 6 / 7 | |
| 1.0.10 | 6 / 7 | |
| 1.0.9 | 6 / 7 | |
| 1.0.8 | 6 / 7 | |
| 1.0.6 | 6 / 7 | |
| 1.0.5 | 6 / 7 | |
| 1.0.4 | 6 / 7 | |
| 1.0.3 | 6 / 7 | |
| 1.0.2 | 6 / 7 | |
| 1.0.1 | 6 / 7 | |
| 1.0.0 | 6 / 7 |
v1.1.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.1.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.0.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.