@finos/legend-application-data-cube-bootstrap
Legend DataCube application bootstrap
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react | AI (phantom-deps): Bootstrap app; react is a peer/runtime dep loaded by the app framework, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only dep; convention-loaded by TypeScript, not directly imported. | ai | |
| phantom-deps | phantom-dep:@finos/legend-data-cube | AI (phantom-deps): Same-org sibling dep in a monorepo bootstrap; indirect usage is expected. | ai | |
| phantom-deps | phantom-dep:@finos/legend-application | AI (phantom-deps): Same-org sibling dep in a monorepo bootstrap; indirect usage is expected. | ai | |
| phantom-deps | phantom-dep:@finos/legend-query-builder | AI (phantom-deps): Same-org sibling dep in a monorepo bootstrap; indirect usage is expected. | ai |
Versions (showing 42 of 242)
| Version | Deps | Published |
|---|---|---|
| 13.41.0 | 7 / 7 | |
| 13.40.0 | 7 / 7 | |
| 13.39.0 | 7 / 7 | |
| 13.38.0 | 7 / 7 | |
| 13.37.0 | 7 / 7 | |
| 13.36.0 | 7 / 7 | |
| 13.35.0 | 7 / 7 | |
| 13.34.0 | 7 / 7 | |
| 13.33.0 | 7 / 7 | |
| 13.32.0 | 7 / 7 | |
| 13.31.0 | 7 / 7 | |
| 13.30.0 | 7 / 7 | |
| 13.29.0 | 7 / 7 | |
| 13.28.0 | 7 / 7 | |
| 13.27.0 | 7 / 7 | |
| 13.26.0 | 7 / 7 | |
| 13.25.0 | 7 / 7 | |
| 13.24.0 | 7 / 7 | |
| 13.23.0 | 7 / 7 | |
| 13.22.0 | 7 / 7 | |
| 13.21.0 | 7 / 7 | |
| 13.20.0 | 7 / 7 | |
| 13.19.0 | 7 / 7 | |
| 13.18.0 | 7 / 7 | |
| 13.17.0 | 7 / 7 | |
| 13.16.0 | 7 / 7 | |
| 13.15.0 | 7 / 7 | |
| 13.14.0 | 7 / 7 | |
| 13.13.0 | 7 / 7 | |
| 13.12.0 | 7 / 7 | |
| 13.11.0 | 7 / 7 | |
| 13.10.0 | 7 / 7 | |
| 13.9.0 | 7 / 7 | |
| 13.8.0 | 7 / 7 | |
| 13.7.0 | 7 / 7 | |
| 13.6.0 | 7 / 7 | |
| 13.5.0 | 7 / 7 | |
| 13.4.0 | 7 / 7 | |
| 13.3.0 | 7 / 7 | |
| 13.2.0 | 7 / 7 | |
| 13.1.0 | 7 / 7 | |
| 13.0.0 | 7 / 7 |
v13.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.