@cubejs-backend/shared
Shared code for Cube.js backend packages
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; sparse README and no keywords are expected for shared backend utilities. | ai | |
| dependencies | unvetted-dep:moment-range | AI (dependencies): moment-range is a legitimate date-range extension; stable dependency in this package across many versions. | ai |
Versions (showing 94 of 194)
| Version | Deps | Published |
|---|---|---|
| 1.3.41 | 15 / 11 | |
| 1.3.40 | 15 / 11 | |
| 1.3.39 | 15 / 11 | |
| 1.3.38 | 15 / 11 | |
| 1.3.37 | 15 / 11 | |
| 1.3.36 | 15 / 11 | |
| 1.3.35 | 15 / 11 | |
| 1.3.34 | 15 / 11 | |
| 1.3.33 | 15 / 11 | |
| 1.3.32 | 15 / 11 | |
| 1.3.31 | 15 / 11 | |
| 1.3.30 | 15 / 11 | |
| 1.3.29 | 15 / 11 | |
| 1.3.28 | 15 / 11 | |
| 1.3.27 | 15 / 11 | |
| 1.3.26 | 15 / 11 | |
| 1.3.25 | 15 / 11 | |
| 1.3.24 | 15 / 11 | |
| 1.3.23 | 15 / 11 | |
| 1.3.22 | 15 / 11 | |
| 1.3.21 | 15 / 11 | |
| 1.3.20 | 15 / 11 | |
| 1.3.19 | 15 / 11 | |
| 1.3.18 | 15 / 11 | |
| 1.3.17 | 15 / 11 | |
| 1.3.16 | 15 / 11 | |
| 1.3.15 | 15 / 11 | |
| 1.3.14 | 15 / 11 | |
| 1.3.13 | 15 / 11 | |
| 1.3.12 | 15 / 11 | |
| 1.3.11 | 15 / 11 | |
| 1.3.10 | 15 / 11 | |
| 1.3.9 | 15 / 11 | |
| 1.3.8 | 15 / 11 | |
| 1.3.7 | 15 / 11 | |
| 1.3.6 | 15 / 11 | |
| 1.3.5 | 15 / 11 | |
| 1.3.4 | 15 / 11 | |
| 1.3.3 | 15 / 11 | |
| 1.3.2 | 15 / 11 | |
| 1.3.1 | 15 / 11 | |
| 1.3.0 | 15 / 11 | |
| 1.2.34 | 15 / 11 | |
| 1.2.33 | 15 / 11 | |
| 1.2.32 | 15 / 11 | |
| 1.2.31 | 15 / 11 | |
| 1.2.30 | 15 / 11 | |
| 1.2.29 | 15 / 11 | |
| 1.2.28 | 15 / 11 | |
| 1.2.27 | 15 / 11 | |
| 1.2.26 | 15 / 11 | |
| 1.2.25 | 15 / 11 | |
| 1.2.24 | 15 / 11 | |
| 1.2.23 | 15 / 11 | |
| 1.2.22 | 15 / 11 | |
| 1.2.21 | 15 / 11 | |
| 1.2.20 | 15 / 11 | |
| 1.2.19 | 15 / 11 | |
| 1.2.18 | 15 / 11 | |
| 1.2.17 | 15 / 11 | |
| 1.2.16 | 14 / 11 | |
| 1.2.15 | 14 / 11 | |
| 1.2.14 | 14 / 11 | |
| 1.2.13 | 14 / 11 | |
| 1.2.12 | 14 / 11 | |
| 1.2.11 | 14 / 11 | |
| 1.2.10 | 14 / 11 | |
| 1.2.9 | 14 / 11 | |
| 1.2.8 | 14 / 11 | |
| 1.2.7 | 14 / 11 | |
| 1.2.6 | 14 / 11 | |
| 1.2.5 | 14 / 11 | |
| 1.2.4 | 14 / 11 | |
| 1.2.3 | 14 / 11 | |
| 1.2.2 | 14 / 11 | |
| 1.2.1 | 14 / 11 | |
| 1.2.0 | 14 / 11 | |
| 1.1.17 | 14 / 11 | |
| 1.1.12 | 14 / 11 | |
| 1.1.10 | 14 / 11 | |
| 1.1.8 | 14 / 11 | |
| 1.1.7 | 14 / 11 | |
| 1.1.4 | 14 / 11 | |
| 1.1.3 | 14 / 11 | |
| 1.1.2 | 14 / 11 | |
| 1.0.12 | 14 / 11 | |
| 1.0.11 | 14 / 11 | |
| 1.0.10 | 14 / 11 | |
| 1.0.9 | 14 / 11 | |
| 1.0.8 | 14 / 11 | |
| 1.0.6 | 14 / 11 | |
| 1.0.3 | 14 / 11 | |
| 1.0.2 | 14 / 11 | |
| 1.0.0 | 14 / 11 |
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.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.