@cubejs-backend/materialize-driver
Cube.js Materialize 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 from statsbot to GitHub Actions CI/CD is consistent with monorepo automation; backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-published release with SLSA attestation in a known monorepo; not indicative of takeover. | ai | |
| phantom-deps | phantom-dep:@types/pg | AI (phantom-deps): @types/pg is a TypeScript type package used at compile time; not imported at runtime by convention. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo driver package; README and metadata style is consistent across the cube-js org, not spam. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/postgres-driver | AI (dependencies): Sibling monorepo package published at the same version; not an external unvetted dependency. | ai |
Versions (showing 100 of 259)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 6 / 3 | |
| 1.4.1 | 6 / 3 | |
| 1.4.0 | 6 / 3 | |
| 1.3.86 | 6 / 3 | |
| 1.3.85 | 6 / 3 | |
| 1.3.84 | 6 / 3 | |
| 1.3.83 | 6 / 3 | |
| 1.3.82 | 6 / 3 | |
| 1.3.81 | 6 / 3 | |
| 1.3.80 | 6 / 3 | |
| 1.3.79 | 6 / 3 | |
| 1.3.78 | 6 / 3 | |
| 1.3.77 | 6 / 3 | |
| 1.3.76 | 6 / 3 | |
| 1.3.75 | 6 / 3 | |
| 1.3.74 | 6 / 3 | |
| 1.3.73 | 6 / 3 | |
| 1.3.72 | 6 / 3 | |
| 1.3.71 | 6 / 3 | |
| 1.3.70 | 6 / 3 | |
| 1.3.69 | 6 / 3 | |
| 1.3.68 | 6 / 3 | |
| 1.3.67 | 6 / 3 | |
| 1.3.66 | 6 / 3 | |
| 1.3.65 | 6 / 3 | |
| 1.3.64 | 6 / 3 | |
| 1.3.63 | 6 / 3 | |
| 1.3.62 | 6 / 3 | |
| 1.3.61 | 6 / 3 | |
| 1.3.60 | 6 / 3 | |
| 1.3.59 | 6 / 3 | |
| 1.3.58 | 6 / 3 | |
| 1.3.57 | 6 / 3 | |
| 1.3.56 | 6 / 3 | |
| 1.3.55 | 6 / 3 | |
| 1.3.54 | 6 / 3 | |
| 1.3.53 | 6 / 3 | |
| 1.3.52 | 6 / 3 | |
| 1.3.51 | 6 / 3 | |
| 1.3.50 | 6 / 3 | |
| 1.3.49 | 6 / 3 | |
| 1.3.48 | 6 / 3 | |
| 1.3.47 | 6 / 3 | |
| 1.3.46 | 6 / 3 | |
| 1.3.45 | 6 / 3 | |
| 1.3.44 | 6 / 3 | |
| 1.3.43 | 6 / 3 | |
| 1.3.42 | 6 / 3 | |
| 1.3.41 | 6 / 3 | |
| 1.3.40 | 6 / 3 | |
| 1.3.39 | 6 / 3 | |
| 1.3.38 | 6 / 3 | |
| 1.3.37 | 6 / 3 | |
| 1.3.36 | 6 / 3 | |
| 1.3.35 | 6 / 3 | |
| 1.3.34 | 6 / 3 | |
| 1.3.33 | 6 / 3 | |
| 1.3.32 | 6 / 3 | |
| 1.3.31 | 6 / 3 | |
| 1.3.30 | 6 / 3 | |
| 1.3.29 | 6 / 3 | |
| 1.3.28 | 6 / 3 | |
| 1.3.27 | 6 / 3 | |
| 1.3.26 | 6 / 3 | |
| 1.3.25 | 6 / 3 | |
| 1.3.24 | 6 / 3 | |
| 1.3.23 | 6 / 3 | |
| 1.3.22 | 6 / 3 | |
| 1.3.21 | 6 / 3 | |
| 1.3.20 | 6 / 3 | |
| 1.3.19 | 6 / 3 | |
| 1.3.18 | 6 / 3 | |
| 1.3.17 | 6 / 3 | |
| 1.3.16 | 6 / 3 | |
| 1.3.15 | 6 / 3 | |
| 1.3.14 | 6 / 3 | |
| 1.3.13 | 6 / 3 | |
| 1.3.12 | 6 / 3 | |
| 1.3.11 | 6 / 3 | |
| 1.3.10 | 6 / 3 | |
| 1.3.9 | 6 / 3 | |
| 1.3.8 | 6 / 3 | |
| 1.3.7 | 6 / 3 | |
| 1.3.6 | 6 / 3 | |
| 1.3.5 | 6 / 3 | |
| 1.3.4 | 6 / 3 | |
| 1.3.3 | 6 / 3 | |
| 1.3.2 | 6 / 3 | |
| 1.3.1 | 6 / 3 | |
| 1.3.0 | 6 / 3 | |
| 1.2.34 | 6 / 3 | |
| 1.2.33 | 6 / 3 | |
| 1.2.32 | 6 / 3 | |
| 1.2.31 | 6 / 3 | |
| 1.2.30 | 6 / 3 | |
| 1.2.29 | 6 / 3 | |
| 1.2.28 | 6 / 3 | |
| 1.2.27 | 6 / 3 | |
| 1.2.26 | 6 / 3 | |
| 1.2.25 | 6 / 3 |
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.