@cubejs-backend/cubestore-driver
Cube Store 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 | no-provenance | AI (provenance): Large established monorepo; provenance absence is consistent across all versions and not a risk indicator here. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Cube.js monorepo with 722 versions; coordinated versioned releases explain any apparent gaps. | ai | |
| dependencies | unvetted-dep:csv-write-stream | AI (dependencies): Long-standing dependency in this package; not newly introduced. | ai | |
| phantom-deps | phantom-dep:generic-pool | AI (phantom-deps): generic-pool is a declared runtime dep; phantom-dep heuristic fires but it is used indirectly via pool abstraction. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README is expected, not a spam indicator. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/base-driver | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/cubestore | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/native | AI (dependencies): Sibling package in the same monorepo/release train; not an independent risk. | ai |
Versions (showing 51 of 152)
| Version | Deps | Published |
|---|---|---|
| 1.2.29 | 13 / 7 | |
| 1.2.28 | 13 / 7 | |
| 1.2.27 | 13 / 7 | |
| 1.2.26 | 13 / 7 | |
| 1.2.25 | 13 / 7 | |
| 1.2.24 | 13 / 7 | |
| 1.2.23 | 13 / 7 | |
| 1.2.22 | 13 / 7 | |
| 1.2.21 | 13 / 7 | |
| 1.2.20 | 13 / 7 | |
| 1.2.19 | 13 / 7 | |
| 1.2.18 | 13 / 7 | |
| 1.2.17 | 13 / 7 | |
| 1.2.16 | 13 / 7 | |
| 1.2.15 | 13 / 7 | |
| 1.2.14 | 13 / 7 | |
| 1.2.13 | 13 / 7 | |
| 1.2.12 | 13 / 7 | |
| 1.2.11 | 13 / 7 | |
| 1.2.10 | 13 / 7 | |
| 1.2.9 | 13 / 7 | |
| 1.2.8 | 13 / 7 | |
| 1.2.7 | 13 / 7 | |
| 1.2.6 | 13 / 7 | |
| 1.2.5 | 13 / 7 | |
| 1.2.4 | 13 / 7 | |
| 1.2.3 | 13 / 7 | |
| 1.2.2 | 13 / 7 | |
| 1.2.1 | 13 / 7 | |
| 1.2.0 | 13 / 7 | |
| 1.1.17 | 13 / 7 | |
| 1.1.16 | 13 / 7 | |
| 1.1.12 | 13 / 7 | |
| 1.1.10 | 13 / 7 | |
| 1.1.9 | 13 / 7 | |
| 1.1.8 | 13 / 7 | |
| 1.1.7 | 13 / 7 | |
| 1.1.5 | 13 / 7 | |
| 1.1.4 | 13 / 7 | |
| 1.1.3 | 13 / 7 | |
| 1.1.2 | 13 / 7 | |
| 1.1.1 | 13 / 7 | |
| 1.0.12 | 13 / 7 | |
| 1.0.11 | 13 / 7 | |
| 1.0.10 | 13 / 7 | |
| 1.0.9 | 13 / 7 | |
| 1.0.8 | 13 / 7 | |
| 1.0.6 | 13 / 7 | |
| 1.0.3 | 13 / 7 | |
| 1.0.2 | 13 / 7 | |
| 1.0.0 | 13 / 7 |
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.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.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.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.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.