@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 100 of 242)
v13.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.