@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 54 of 159)
| Version | Deps | Published |
|---|---|---|
| 1.3.62 | 8 / 1 | |
| 1.3.61 | 8 / 1 | |
| 1.3.60 | 8 / 1 | |
| 1.3.59 | 8 / 1 | |
| 1.3.58 | 8 / 1 | |
| 1.3.57 | 8 / 1 | |
| 1.3.56 | 8 / 1 | |
| 1.3.55 | 8 / 1 | |
| 1.3.54 | 8 / 1 | |
| 1.3.53 | 8 / 1 | |
| 1.3.52 | 8 / 1 | |
| 1.3.51 | 8 / 1 | |
| 1.3.50 | 8 / 1 | |
| 1.3.49 | 8 / 1 | |
| 1.3.48 | 8 / 1 | |
| 1.3.47 | 8 / 1 | |
| 1.3.46 | 8 / 1 | |
| 1.3.45 | 8 / 1 | |
| 1.3.44 | 8 / 1 | |
| 1.3.43 | 8 / 1 | |
| 1.3.42 | 8 / 1 | |
| 1.3.41 | 8 / 1 | |
| 1.3.40 | 8 / 1 | |
| 1.3.39 | 8 / 1 | |
| 1.3.38 | 8 / 1 | |
| 1.3.37 | 8 / 1 | |
| 1.3.36 | 8 / 1 | |
| 1.3.35 | 8 / 1 | |
| 1.3.34 | 8 / 1 | |
| 1.3.33 | 8 / 1 | |
| 1.3.32 | 8 / 1 | |
| 1.3.31 | 8 / 1 | |
| 1.3.30 | 8 / 1 | |
| 1.3.29 | 8 / 1 | |
| 1.3.28 | 8 / 1 | |
| 1.3.27 | 8 / 1 | |
| 1.3.26 | 8 / 1 | |
| 1.3.25 | 8 / 1 | |
| 1.3.24 | 8 / 1 | |
| 1.3.23 | 8 / 1 | |
| 1.3.22 | 8 / 1 | |
| 1.3.21 | 8 / 1 | |
| 1.3.20 | 8 / 1 | |
| 1.3.19 | 8 / 1 | |
| 1.3.18 | 8 / 1 | |
| 1.3.17 | 8 / 1 | |
| 1.3.16 | 8 / 1 | |
| 1.3.15 | 8 / 1 | |
| 1.3.14 | 8 / 1 | |
| 1.3.13 | 8 / 1 | |
| 1.3.12 | 8 / 1 | |
| 1.3.11 | 8 / 1 | |
| 1.0.14 | 8 / 1 | |
| 1.0.13 | 8 / 1 |
v1.3.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
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.
v1.0.14
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.13
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.