@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 51 of 121)
| Version | Deps | Published |
|---|---|---|
| 1.7.11 | 16 / 21 | |
| 1.7.10 | 16 / 21 | |
| 1.7.8 | 16 / 21 | |
| 1.7.7 | 16 / 21 | |
| 1.7.6 | 16 / 21 | |
| 1.7.5 | 16 / 21 | |
| 1.7.4 | 16 / 21 | |
| 1.7.3 | 16 / 21 | |
| 1.7.2 | 16 / 21 | |
| 1.7.1 | 16 / 21 | |
| 1.7.0 | 16 / 21 | |
| 1.6.69 | 16 / 21 | |
| 1.6.68 | 16 / 21 | |
| 1.6.67 | 16 / 21 | |
| 1.6.66 | 16 / 21 | |
| 1.6.65 | 16 / 21 | |
| 1.6.64 | 16 / 21 | |
| 1.6.63 | 16 / 21 | |
| 1.6.62 | 16 / 21 | |
| 1.6.61 | 16 / 21 | |
| 1.6.60 | 16 / 21 | |
| 1.6.59 | 16 / 21 | |
| 1.6.58 | 16 / 21 | |
| 1.6.57 | 16 / 21 | |
| 1.6.56 | 16 / 21 | |
| 1.6.55 | 16 / 21 | |
| 1.6.54 | 16 / 21 | |
| 1.6.53 | 16 / 21 | |
| 1.6.52 | 16 / 21 | |
| 1.6.51 | 16 / 21 | |
| 1.6.50 | 16 / 21 | |
| 1.6.49 | 16 / 21 | |
| 1.6.48 | 16 / 21 | |
| 1.6.47 | 16 / 21 | |
| 1.6.44 | 16 / 21 | |
| 1.6.43 | 16 / 21 | |
| 1.6.12 | 16 / 21 | |
| 1.5.11 | 16 / 21 | |
| 1.5.7 | 16 / 21 | |
| 1.5.2 | 16 / 21 | |
| 1.4.3 | 16 / 21 | |
| 1.3.37 | 16 / 21 | |
| 1.3.26 | 16 / 21 | |
| 1.3.25 | 16 / 21 | |
| 1.3.10 | 16 / 21 | |
| 1.3.9 | 16 / 21 | |
| 1.3.8 | 16 / 21 | |
| 1.3.7 | 16 / 21 | |
| 1.3.6 | 16 / 21 | |
| 1.3.5 | 16 / 21 | |
| 1.3.4 | 16 / 21 |
v1.7.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.