@cubejs-backend/query-orchestrator
Cube.js Query Orchestrator and Cache
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Cube.js monorepo with SLSA provenance; dormancy pattern consistent with coordinated versioned releases, not takeover. | ai | |
| dependencies | unvetted-dep:csv-write-stream | AI (dependencies): csv-write-stream is a legitimate utility; stable dependency in this well-established Cube.js package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; README and metadata patterns are typical for internal packages, not spam. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/base-driver | AI (dependencies): Sibling monorepo package published at same version; not an independent unvetted dependency. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/cubestore-driver | AI (dependencies): Sibling monorepo package published at same version; not an independent unvetted dependency. | ai |
Versions (showing 86 of 186)
| Version | Deps | Published |
|---|---|---|
| 1.3.49 | 6 / 7 | |
| 1.3.48 | 6 / 7 | |
| 1.3.47 | 6 / 7 | |
| 1.3.46 | 6 / 7 | |
| 1.3.45 | 6 / 7 | |
| 1.3.44 | 6 / 7 | |
| 1.3.43 | 6 / 7 | |
| 1.3.42 | 6 / 7 | |
| 1.3.41 | 6 / 7 | |
| 1.3.40 | 6 / 7 | |
| 1.3.39 | 7 / 8 | |
| 1.3.38 | 7 / 8 | |
| 1.3.37 | 7 / 8 | |
| 1.3.36 | 7 / 8 | |
| 1.3.35 | 7 / 8 | |
| 1.3.34 | 7 / 8 | |
| 1.3.33 | 7 / 8 | |
| 1.3.32 | 7 / 8 | |
| 1.3.31 | 7 / 8 | |
| 1.3.30 | 7 / 8 | |
| 1.3.29 | 7 / 8 | |
| 1.3.28 | 7 / 8 | |
| 1.3.27 | 7 / 8 | |
| 1.3.26 | 7 / 8 | |
| 1.3.25 | 7 / 8 | |
| 1.3.24 | 7 / 8 | |
| 1.3.23 | 7 / 8 | |
| 1.3.22 | 7 / 8 | |
| 1.3.21 | 7 / 8 | |
| 1.3.20 | 7 / 8 | |
| 1.3.19 | 7 / 8 | |
| 1.3.18 | 7 / 8 | |
| 1.3.17 | 7 / 8 | |
| 1.3.16 | 7 / 8 | |
| 1.3.15 | 7 / 8 | |
| 1.3.14 | 7 / 8 | |
| 1.3.13 | 7 / 8 | |
| 1.3.12 | 7 / 8 | |
| 1.3.11 | 7 / 8 | |
| 1.3.10 | 7 / 8 | |
| 1.3.9 | 7 / 8 | |
| 1.3.8 | 7 / 8 | |
| 1.3.7 | 7 / 8 | |
| 1.3.6 | 7 / 8 | |
| 1.3.5 | 7 / 8 | |
| 1.3.4 | 7 / 8 | |
| 1.3.3 | 7 / 8 | |
| 1.3.2 | 7 / 8 | |
| 1.3.1 | 7 / 8 | |
| 1.3.0 | 7 / 8 | |
| 1.2.34 | 7 / 8 | |
| 1.2.33 | 7 / 8 | |
| 1.2.32 | 7 / 8 | |
| 1.2.31 | 7 / 8 | |
| 1.2.30 | 7 / 8 | |
| 1.2.29 | 7 / 8 | |
| 1.2.28 | 7 / 8 | |
| 1.2.27 | 7 / 8 | |
| 1.2.26 | 7 / 8 | |
| 1.2.25 | 7 / 8 | |
| 1.2.24 | 7 / 8 | |
| 1.2.23 | 7 / 8 | |
| 1.2.22 | 7 / 8 | |
| 1.2.21 | 7 / 8 | |
| 1.2.20 | 7 / 8 | |
| 1.2.19 | 7 / 8 | |
| 1.2.18 | 7 / 8 | |
| 1.2.17 | 7 / 8 | |
| 1.2.16 | 7 / 8 | |
| 1.2.15 | 7 / 8 | |
| 1.2.14 | 7 / 8 | |
| 1.2.13 | 7 / 8 | |
| 1.2.12 | 7 / 8 | |
| 1.2.11 | 7 / 8 | |
| 1.2.10 | 7 / 8 | |
| 1.2.9 | 7 / 8 | |
| 1.2.8 | 7 / 8 | |
| 1.2.7 | 7 / 8 | |
| 1.2.6 | 7 / 8 | |
| 1.2.5 | 8 / 8 | |
| 1.2.4 | 8 / 8 | |
| 1.2.3 | 8 / 8 | |
| 1.2.2 | 8 / 8 | |
| 1.2.1 | 8 / 8 | |
| 1.2.0 | 8 / 8 | |
| 1.1.17 | 8 / 8 |
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.
v1.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.