@cubejs-backend/testing-shared
Cube.js Testing Helpers
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): SLSA provenance attestation via CI/CD confirms legitimate publish; monorepo package with long release history. | ai | |
| dependencies | unvetted-dep:@testcontainers/kafka | AI (dependencies): Testing-only container helper; expected dependency for a testing-shared package in the Cube.js ecosystem. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/dotenv | AI (dependencies): Same org scope (@cubejs-backend); stable internal dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Cube.js monorepo consistently publishes without Sigstore provenance; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo testing helper; sparse README is expected for internal packages, not a spam/phishing indicator. | ai | |
| phantom-deps | phantom-dep:@cubejs-backend/dotenv | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo internal deps. | ai |
Versions (showing 57 of 259)
| Version | Deps | Published |
|---|---|---|
| 1.2.24 | 8 / 7 | |
| 1.2.23 | 8 / 7 | |
| 1.2.22 | 8 / 7 | |
| 1.2.21 | 8 / 7 | |
| 1.2.20 | 8 / 7 | |
| 1.2.19 | 8 / 7 | |
| 1.2.18 | 8 / 7 | |
| 1.2.17 | 8 / 7 | |
| 1.2.16 | 8 / 7 | |
| 1.2.15 | 8 / 7 | |
| 1.2.14 | 8 / 7 | |
| 1.2.13 | 8 / 7 | |
| 1.2.12 | 8 / 7 | |
| 1.2.11 | 8 / 7 | |
| 1.2.10 | 8 / 7 | |
| 1.2.9 | 8 / 7 | |
| 1.2.8 | 8 / 7 | |
| 1.2.7 | 8 / 7 | |
| 1.2.6 | 8 / 7 | |
| 1.2.5 | 8 / 7 | |
| 1.2.4 | 8 / 7 | |
| 1.2.3 | 8 / 7 | |
| 1.2.2 | 8 / 7 | |
| 1.2.1 | 8 / 7 | |
| 1.2.0 | 8 / 7 | |
| 1.1.17 | 8 / 7 | |
| 1.1.16 | 8 / 7 | |
| 1.1.15 | 8 / 7 | |
| 1.1.14 | 8 / 7 | |
| 1.1.13 | 8 / 7 | |
| 1.1.12 | 8 / 7 | |
| 1.1.11 | 8 / 7 | |
| 1.1.10 | 8 / 7 | |
| 1.1.9 | 8 / 7 | |
| 1.1.8 | 8 / 7 | |
| 1.1.7 | 8 / 7 | |
| 1.1.6 | 8 / 7 | |
| 1.1.5 | 8 / 7 | |
| 1.1.4 | 8 / 7 | |
| 1.1.3 | 8 / 7 | |
| 1.1.2 | 8 / 7 | |
| 1.1.1 | 8 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.14 | 8 / 7 | |
| 1.0.13 | 8 / 7 | |
| 1.0.12 | 8 / 7 | |
| 1.0.11 | 8 / 7 | |
| 1.0.10 | 8 / 7 | |
| 1.0.9 | 8 / 7 | |
| 1.0.8 | 8 / 7 | |
| 1.0.6 | 8 / 7 | |
| 1.0.5 | 8 / 7 | |
| 1.0.4 | 8 / 7 | |
| 1.0.3 | 8 / 7 | |
| 1.0.2 | 8 / 7 | |
| 1.0.1 | 8 / 7 | |
| 1.0.0 | 8 / 7 |
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.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.1.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.1.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.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.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.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.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.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.1.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.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.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.0.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.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.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.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.