@cubejs-backend/prestodb-driver
Cube.js Presto 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 | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is consistent with SLSA-attested CI/CD pipeline for the cube-js monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms legitimate CI/CD publish; part of cube-js monorepo with 556 prior versions. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo package; provenance absence is consistent across all cube-js packages. | ai | |
| dependencies | unvetted-dep:presto-client | AI (dependencies): presto-client is the canonical dependency for this Presto driver; stable across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; README style and missing keywords are normal for this package family. | ai |
Versions (showing 80 of 180)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 5 / 6 | |
| 1.4.3 | 5 / 6 | |
| 1.4.2 | 5 / 6 | |
| 1.4.1 | 5 / 6 | |
| 1.4.0 | 5 / 6 | |
| 1.3.86 | 5 / 6 | |
| 1.3.85 | 5 / 6 | |
| 1.3.84 | 5 / 6 | |
| 1.3.83 | 5 / 6 | |
| 1.3.82 | 5 / 6 | |
| 1.3.81 | 5 / 6 | |
| 1.3.80 | 5 / 6 | |
| 1.3.79 | 5 / 6 | |
| 1.3.10 | 5 / 6 | |
| 1.3.9 | 5 / 6 | |
| 1.3.8 | 5 / 6 | |
| 1.3.7 | 5 / 6 | |
| 1.3.6 | 5 / 6 | |
| 1.3.5 | 5 / 6 | |
| 1.3.4 | 5 / 6 | |
| 1.3.3 | 5 / 6 | |
| 1.3.2 | 5 / 6 | |
| 1.3.1 | 5 / 6 | |
| 1.3.0 | 5 / 6 | |
| 1.2.34 | 5 / 6 | |
| 1.2.33 | 5 / 6 | |
| 1.2.32 | 5 / 6 | |
| 1.2.31 | 5 / 6 | |
| 1.2.30 | 5 / 6 | |
| 1.2.29 | 5 / 6 | |
| 1.2.28 | 5 / 6 | |
| 1.2.27 | 5 / 6 | |
| 1.2.26 | 5 / 6 | |
| 1.2.25 | 5 / 6 | |
| 1.2.24 | 5 / 6 | |
| 1.2.23 | 5 / 6 | |
| 1.2.22 | 5 / 6 | |
| 1.2.21 | 5 / 6 | |
| 1.2.20 | 5 / 6 | |
| 1.2.19 | 5 / 6 | |
| 1.2.18 | 5 / 6 | |
| 1.2.17 | 5 / 6 | |
| 1.2.16 | 5 / 6 | |
| 1.2.15 | 5 / 6 | |
| 1.2.14 | 5 / 6 | |
| 1.2.13 | 5 / 6 | |
| 1.2.12 | 5 / 6 | |
| 1.2.11 | 5 / 6 | |
| 1.2.10 | 5 / 6 | |
| 1.2.9 | 5 / 6 | |
| 1.2.8 | 5 / 6 | |
| 1.2.7 | 5 / 6 | |
| 1.2.6 | 5 / 6 | |
| 1.2.5 | 5 / 6 | |
| 1.2.4 | 5 / 6 | |
| 1.2.3 | 5 / 6 | |
| 1.2.2 | 5 / 6 | |
| 1.2.1 | 5 / 6 | |
| 1.2.0 | 5 / 6 | |
| 1.1.17 | 5 / 6 | |
| 1.1.16 | 5 / 6 | |
| 1.1.12 | 5 / 6 | |
| 1.1.10 | 5 / 6 | |
| 1.1.8 | 5 / 6 | |
| 1.1.7 | 5 / 6 | |
| 1.1.4 | 5 / 6 | |
| 1.1.3 | 5 / 6 | |
| 1.1.2 | 5 / 6 | |
| 1.1.1 | 5 / 6 | |
| 1.0.14 | 5 / 6 | |
| 1.0.13 | 5 / 6 | |
| 1.0.12 | 5 / 6 | |
| 1.0.11 | 5 / 6 | |
| 1.0.10 | 5 / 6 | |
| 1.0.9 | 5 / 6 | |
| 1.0.8 | 5 / 6 | |
| 1.0.6 | 5 / 6 | |
| 1.0.3 | 5 / 6 | |
| 1.0.2 | 5 / 6 | |
| 1.0.0 | 5 / 6 |
v1.3.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.3.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.3.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.3.7
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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.2.34
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.2.33
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.2.32
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.2.31
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.2.30
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.2.29
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.2.28
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.2.27
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.2.26
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.2.25
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.2.24
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.2.23
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.2.22
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.2.21
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.2.20
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.2.19
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.2.18
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.2.17
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.2.16
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.2.15
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.2.14
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.2.13
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.2.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.2.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.2.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.2.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.2.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.2.7
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.2.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.2.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.2.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.2.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.2.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.2.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.2.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.1.17
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.16
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.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.1.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.1.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.1.7
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.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.1.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.1.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.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.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.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.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.