@cubejs-backend/hive-driver
Cube.js Hive 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:jshs2 | AI (dependencies): Expected Hive Thrift client dependency for this Hive database driver; stable across versions. | ai | |
| dependencies | unvetted-dep:sasl-plain | AI (dependencies): Expected SASL authentication dependency for Hive connections; stable across versions. | ai | |
| dependencies | unvetted-dep:saslmechanisms | AI (dependencies): Expected SASL mechanisms dependency for Hive connections; stable across versions. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is consistent with cube-js monorepo automation, backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Cube-js monorepo; dormancy reflects driver-specific inactivity, not account takeover — SLSA attestation confirms legitimate CI release. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo driver package; README links are to Cube.js docs, not a phishing farm. | ai |
Versions (showing 48 of 248)
| Version | Deps | Published |
|---|---|---|
| 1.2.26 | 8 / 1 | |
| 1.2.25 | 8 / 1 | |
| 1.2.24 | 8 / 1 | |
| 1.2.23 | 8 / 1 | |
| 1.2.22 | 8 / 1 | |
| 1.2.21 | 8 / 1 | |
| 1.2.20 | 8 / 1 | |
| 1.2.19 | 8 / 1 | |
| 1.2.18 | 8 / 1 | |
| 1.2.17 | 8 / 1 | |
| 1.2.16 | 8 / 1 | |
| 1.2.15 | 8 / 1 | |
| 1.2.14 | 8 / 1 | |
| 1.2.13 | 8 / 1 | |
| 1.2.12 | 8 / 1 | |
| 1.2.11 | 8 / 1 | |
| 1.2.10 | 8 / 1 | |
| 1.2.9 | 8 / 1 | |
| 1.2.8 | 8 / 1 | |
| 1.2.7 | 8 / 1 | |
| 1.2.6 | 8 / 1 | |
| 1.2.5 | 8 / 1 | |
| 1.2.4 | 8 / 1 | |
| 1.2.3 | 8 / 1 | |
| 1.2.2 | 8 / 1 | |
| 1.2.1 | 8 / 1 | |
| 1.2.0 | 8 / 1 | |
| 1.1.17 | 8 / 1 | |
| 1.1.16 | 8 / 1 | |
| 1.1.12 | 8 / 1 | |
| 1.1.10 | 8 / 1 | |
| 1.1.8 | 8 / 1 | |
| 1.1.7 | 8 / 1 | |
| 1.1.4 | 8 / 1 | |
| 1.1.3 | 8 / 1 | |
| 1.1.2 | 8 / 1 | |
| 1.1.1 | 8 / 1 | |
| 1.0.14 | 8 / 1 | |
| 1.0.13 | 8 / 1 | |
| 1.0.12 | 8 / 1 | |
| 1.0.11 | 8 / 1 | |
| 1.0.10 | 8 / 1 | |
| 1.0.9 | 8 / 1 | |
| 1.0.8 | 8 / 1 | |
| 1.0.6 | 8 / 1 | |
| 1.0.3 | 8 / 1 | |
| 1.0.2 | 8 / 1 | |
| 1.0.0 | 8 / 1 |
v1.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.