@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 100 of 151)
| Version | Deps | Published |
|---|---|---|
| 1.7.12 | 12 / 7 | |
| 1.7.11 | 12 / 7 | |
| 1.7.10 | 12 / 7 | |
| 1.7.9 | 12 / 7 | |
| 1.7.8 | 12 / 7 | |
| 1.7.7 | 12 / 7 | |
| 1.7.6 | 12 / 7 | |
| 1.7.5 | 12 / 7 | |
| 1.7.4 | 12 / 7 | |
| 1.7.3 | 12 / 7 | |
| 1.7.2 | 12 / 7 | |
| 1.7.1 | 12 / 7 | |
| 1.7.0 | 12 / 7 | |
| 1.6.69 | 12 / 7 | |
| 1.6.68 | 12 / 7 | |
| 1.6.67 | 12 / 7 | |
| 1.6.66 | 12 / 7 | |
| 1.6.65 | 12 / 7 | |
| 1.6.64 | 12 / 7 | |
| 1.6.63 | 12 / 7 | |
| 1.6.62 | 12 / 7 | |
| 1.6.61 | 12 / 7 | |
| 1.6.60 | 12 / 7 | |
| 1.6.59 | 12 / 7 | |
| 1.6.58 | 12 / 7 | |
| 1.6.57 | 12 / 7 | |
| 1.6.56 | 12 / 7 | |
| 1.6.55 | 12 / 7 | |
| 1.6.54 | 12 / 7 | |
| 1.6.53 | 12 / 7 | |
| 1.6.52 | 12 / 7 | |
| 1.6.51 | 12 / 7 | |
| 1.6.50 | 12 / 7 | |
| 1.6.49 | 12 / 7 | |
| 1.6.48 | 12 / 7 | |
| 1.6.47 | 12 / 7 | |
| 1.6.46 | 12 / 7 | |
| 1.6.45 | 12 / 7 | |
| 1.6.44 | 12 / 7 | |
| 1.6.43 | 12 / 7 | |
| 1.6.42 | 12 / 7 | |
| 1.6.41 | 12 / 7 | |
| 1.6.40 | 12 / 7 | |
| 1.6.39 | 12 / 7 | |
| 1.6.38 | 12 / 7 | |
| 1.6.37 | 12 / 7 | |
| 1.6.36 | 12 / 7 | |
| 1.6.35 | 12 / 7 | |
| 1.6.34 | 12 / 7 | |
| 1.6.33 | 12 / 7 | |
| 1.6.32 | 12 / 7 | |
| 1.6.31 | 12 / 7 | |
| 1.6.30 | 12 / 7 | |
| 1.6.29 | 12 / 7 | |
| 1.6.28 | 12 / 7 | |
| 1.6.27 | 12 / 7 | |
| 1.6.26 | 12 / 7 | |
| 1.6.25 | 12 / 7 | |
| 1.6.24 | 12 / 7 | |
| 1.6.23 | 12 / 7 | |
| 1.5.13 | 13 / 7 | |
| 1.5.12 | 13 / 7 | |
| 1.5.11 | 13 / 7 | |
| 1.5.10 | 13 / 7 | |
| 1.5.9 | 13 / 7 | |
| 1.5.8 | 13 / 7 | |
| 1.5.7 | 13 / 7 | |
| 1.5.6 | 13 / 7 | |
| 1.5.5 | 13 / 7 | |
| 1.5.4 | 13 / 7 | |
| 1.5.3 | 13 / 7 | |
| 1.4.3 | 13 / 7 | |
| 1.3.86 | 13 / 7 | |
| 1.3.72 | 13 / 7 | |
| 1.3.66 | 13 / 7 | |
| 1.3.63 | 13 / 7 | |
| 1.3.57 | 13 / 7 | |
| 1.3.34 | 13 / 8 | |
| 1.3.31 | 13 / 8 | |
| 1.3.30 | 13 / 8 | |
| 1.3.28 | 13 / 8 | |
| 1.3.26 | 13 / 8 | |
| 1.3.18 | 13 / 8 | |
| 1.3.12 | 13 / 8 | |
| 1.3.10 | 13 / 8 | |
| 1.3.9 | 13 / 8 | |
| 1.3.8 | 13 / 7 | |
| 1.3.7 | 13 / 7 | |
| 1.3.6 | 13 / 7 | |
| 1.3.5 | 13 / 7 | |
| 1.3.4 | 13 / 7 | |
| 1.3.3 | 13 / 7 | |
| 1.3.2 | 13 / 7 | |
| 1.3.1 | 13 / 7 | |
| 1.3.0 | 13 / 7 | |
| 1.2.34 | 13 / 7 | |
| 1.2.33 | 13 / 7 | |
| 1.2.32 | 13 / 7 | |
| 1.2.31 | 13 / 7 | |
| 1.2.30 | 13 / 7 |
v1.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.