@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 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 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.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 |
v1.6.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.52
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.51
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.50
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.49
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.48
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.47
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.46
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.45
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.44
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.43
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
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.