@finos/legend-application-data-cube
Legend DataCube application core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:serializr | AI (dependencies): Well-known serialization library; stable dependency of Legend ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-art | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:react-oidc-context | AI (dependencies): Established OIDC React library; no known advisories. | ai | |
| dependencies | unvetted-dep:@duckdb/duckdb-wasm | AI (dependencies): Official DuckDB WASM package from the DuckDB org. | ai | |
| dependencies | unvetted-dep:@finos/legend-graph | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-shared | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-storage | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-data-cube | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-application | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-code-editor | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-server-depot | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-query-builder | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@finos/legend-server-lakehouse | AI (dependencies): Core FINOS Legend monorepo package; no malware indicators. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only package loaded by convention in React projects; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only package loaded by convention in React projects; stable false positive. | ai |
Versions (showing 51 of 135)
| Version | Deps | Published |
|---|---|---|
| 0.7.78 | 21 / 11 | |
| 0.7.77 | 21 / 11 | |
| 0.7.76 | 21 / 11 | |
| 0.7.75 | 21 / 11 | |
| 0.7.74 | 21 / 11 | |
| 0.7.73 | 21 / 11 | |
| 0.7.72 | 21 / 11 | |
| 0.7.71 | 21 / 11 | |
| 0.7.70 | 21 / 11 | |
| 0.7.69 | 21 / 11 | |
| 0.7.68 | 21 / 11 | |
| 0.7.67 | 21 / 11 | |
| 0.7.66 | 21 / 11 | |
| 0.7.65 | 21 / 11 | |
| 0.7.64 | 21 / 11 | |
| 0.7.60 | 21 / 11 | |
| 0.7.58 | 21 / 11 | |
| 0.7.56 | 21 / 11 | |
| 0.7.55 | 21 / 11 | |
| 0.7.54 | 21 / 11 | |
| 0.7.53 | 21 / 11 | |
| 0.7.52 | 21 / 11 | |
| 0.7.50 | 21 / 11 | |
| 0.7.49 | 21 / 11 | |
| 0.7.48 | 21 / 11 | |
| 0.7.47 | 21 / 11 | |
| 0.7.44 | 21 / 11 | |
| 0.7.42 | 21 / 11 | |
| 0.7.41 | 21 / 11 | |
| 0.7.40 | 21 / 11 | |
| 0.7.39 | 21 / 11 | |
| 0.7.37 | 21 / 11 | |
| 0.7.36 | 21 / 11 | |
| 0.7.34 | 21 / 11 | |
| 0.7.33 | 21 / 11 | |
| 0.7.32 | 21 / 11 | |
| 0.7.31 | 21 / 11 | |
| 0.7.28 | 21 / 11 | |
| 0.7.26 | 21 / 11 | |
| 0.7.25 | 21 / 11 | |
| 0.7.24 | 21 / 11 | |
| 0.7.23 | 21 / 11 | |
| 0.7.22 | 21 / 11 | |
| 0.7.20 | 21 / 11 | |
| 0.7.19 | 21 / 11 | |
| 0.7.18 | 21 / 11 | |
| 0.7.17 | 21 / 11 | |
| 0.7.15 | 21 / 11 | |
| 0.7.14 | 21 / 11 | |
| 0.7.13 | 21 / 11 | |
| 0.7.12 | 21 / 11 |
v0.7.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.