@finos/legend-data-cube Apache-2.0 18 versions

@finos/legend-data-cube

npm Repository Homepage

Legend DataCube

18

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

finos-adminmaootexodusneil.slinger

Keywords

legendlegend-data-cubedata-cube

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:shady-links-tlds	AI (semgrep): Flagged URL is clrs.cc in a code comment referencing a legitimate CSS color palette; not C2/exfiltration.	ai	2026/04/29
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): react-dom is a standard peer/runtime dep for React packages; phantom-dep heuristic is a false positive here.	ai	2026/04/29
phantom-deps	phantom-dep:@types/react	AI (phantom-deps): Type-only package loaded by convention in TypeScript projects; not directly imported.	ai	2026/04/29

Versions (showing 18 of 120)

Version	Deps	Published
0.2.11	15 / 9	2025-05-30
0.2.10	15 / 9	2025-05-30
0.2.9	15 / 9	2025-05-29
0.2.8	15 / 9	2025-05-27
0.2.7	15 / 9	2025-05-26
0.2.6	15 / 9	2025-05-23
0.2.5	15 / 9	2025-05-22
0.2.4	15 / 9	2025-05-20
0.2.3	15 / 9	2025-05-19
0.2.2	15 / 9	2025-05-16
0.2.1	15 / 9	2025-05-14
0.2.0	15 / 9	2025-05-13
0.1.32	15 / 9	2025-05-08
0.1.31	15 / 9	2025-05-07
0.1.30	15 / 9	2025-05-05
0.1.29	15 / 9	2025-05-01
0.1.28	15 / 9	2025-05-01
0.1.27	15 / 9	2025-05-01

v0.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.