@cubejs-backend/testing
Cube.js e2e tests
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; CI/CD publisher consistent with org's release pattern. | ai | |
| dependencies | unvetted-dep:http-proxy | AI (dependencies): Standard proxy utility used in Cube.js testing infra; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@cubejs-backend/dotenv | AI (dependencies): Same org scope (@cubejs-backend); internal fork of dotenv used across the monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance not yet adopted across all packages. | ai | |
| phantom-deps | phantom-dep:dedent | AI (phantom-deps): Testing utility; config-file reference pattern is stable false positive. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Testing utility; config-file reference pattern is stable false positive. | ai | |
| phantom-deps | phantom-dep:@cubejs-backend/dotenv | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal testing package in a large monorepo; minimal README and no keywords are expected. | ai | |
| phantom-deps | phantom-dep:@cubejs-client/ws-transport | AI (phantom-deps): Testing utility; config-file reference pattern is stable false positive. | ai | |
| phantom-deps | phantom-dep:@cubejs-backend/schema-compiler | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cubejs-backend/cubestore-driver | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cubejs-backend/query-orchestrator | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai |
Versions (showing 21 of 123)
| Version | Deps | Published |
|---|---|---|
| 1.1.7 | 16 / 21 | |
| 1.1.6 | 16 / 21 | |
| 1.1.5 | 16 / 21 | |
| 1.1.4 | 16 / 21 | |
| 1.1.3 | 16 / 21 | |
| 1.1.2 | 16 / 21 | |
| 1.1.1 | 16 / 21 | |
| 1.1.0 | 16 / 21 | |
| 1.0.12 | 16 / 21 | |
| 1.0.11 | 16 / 21 | |
| 1.0.10 | 16 / 21 | |
| 1.0.9 | 16 / 21 | |
| 1.0.8 | 16 / 21 | |
| 1.0.7 | 16 / 21 | |
| 1.0.6 | 16 / 21 | |
| 1.0.5 | 16 / 21 | |
| 1.0.4 | 16 / 21 | |
| 1.0.3 | 16 / 21 | |
| 1.0.2 | 16 / 21 | |
| 1.0.1 | 16 / 21 | |
| 1.0.0 | 16 / 21 |
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.