@cubejs-backend/jdbc-driver
Cube.js JDBC 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:java | AI (dependencies): Standard JDBC bridge dep required for this driver's stated function. | ai | |
| dependencies | unvetted-dep:node-java-maven | AI (dependencies): Build helper for java native bindings, expected for this package type. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/jdbc | AI (dependencies): Official cube.js sibling package, optional dep. | ai | |
| phantom-deps | phantom-dep:java | AI (phantom-deps): Used via config/native binding, not direct import; expected for java bridge. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; part of large established monorepo with 535 versions. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/node-java-maven | AI (dependencies): First-party Cube.js package; stable internal dependency across all versions of this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; README linking to main project docs is expected, not a phishing indicator. | ai |
Versions (showing 6 of 206)
| Version | Deps | Published |
|---|---|---|
| 1.2.26 | 5 / 5 | |
| 1.2.25 | 5 / 5 | |
| 1.2.24 | 5 / 5 | |
| 1.2.23 | 5 / 5 | |
| 1.0.11 | 7 / 6 | |
| 1.0.2 | 7 / 6 |
v1.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.