@cubejs-backend/databricks-jdbc-driver
Cube.js Databricks 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): Established Cube.js package; lack of Sigstore provenance is consistent across all versions and poses no elevated risk here. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active monorepo with 683 versions; CI/CD publishing with SLSA provenance; dormancy flag is a false positive here. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): JDBC driver binary fetch via postinstall is documented and consistent across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Cube.js monorepo package; README link density and missing keywords are false positives for this established OSS project. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dep; phantom-dep heuristic misfires for this package. | ai | |
| phantom-deps | phantom-dep:ramda | AI (phantom-deps): ramda is a declared runtime dep; phantom-dep heuristic misfires for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.6.47 | 8 / 7 | |
| 1.6.44 | 8 / 7 | |
| 1.6.43 | 8 / 7 | |
| 1.5.4 | 8 / 7 | |
| 1.5.3 | 8 / 7 | |
| 1.5.2 | 8 / 7 | |
| 1.3.11 | 8 / 8 |
v1.6.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.43
2 findingsScript: node bin/post-install
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.