← Home

@finos/legend-extension-dsl-data-quality

Legend extension for Data Quality

9
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-extensiondsldsl-data-quality

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established FINOS org package; lack of Sigstore provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): React framework package declared for bundler/type resolution; stable false positive for this package. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): Type-only declaration; loaded by convention in React projects. ai
phantom-deps phantom-dep:@types/react-dom AI (phantom-deps): Type-only declaration; loaded by convention in React projects. ai
phantom-deps phantom-dep:@finos/legend-storage AI (phantom-deps): Same-org sibling package; phantom-dep heuristic is unreliable for monorepo packages. ai

Versions (showing 9 of 110)

Version Deps Published
2.0.71 18 / 9
2.0.70 18 / 9
2.0.69 18 / 9
2.0.68 18 / 9
2.0.67 18 / 9
2.0.66 18 / 9
2.0.65 18 / 9
2.0.64 18 / 9
2.0.63 18 / 9

v2.0.71

1 finding
INFO No provenance attestation provenance

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

v2.0.70

1 finding
INFO No provenance attestation provenance

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

v2.0.69

1 finding
INFO No provenance attestation provenance

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

v2.0.68

1 finding
INFO No provenance attestation provenance

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

v2.0.67

1 finding
INFO No provenance attestation provenance

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

v2.0.66

1 finding
INFO No provenance attestation provenance

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

v2.0.65

1 finding
INFO No provenance attestation provenance

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

v2.0.64

1 finding
INFO No provenance attestation provenance

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

v2.0.63

1 finding
INFO No provenance attestation provenance

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