@finos/legend-extension-dsl-data-quality
Legend extension for Data Quality
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 |
|---|---|---|---|---|
| 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 100 of 240)
| Version | Deps | Published |
|---|---|---|
| 2.1.65 | 18 / 9 | |
| 2.1.64 | 18 / 9 | |
| 2.1.63 | 18 / 9 | |
| 2.1.62 | 18 / 9 | |
| 2.1.61 | 18 / 9 | |
| 2.1.60 | 18 / 9 | |
| 2.1.59 | 18 / 9 | |
| 2.1.58 | 18 / 9 | |
| 2.1.57 | 18 / 9 | |
| 2.1.56 | 18 / 9 | |
| 2.1.55 | 18 / 9 | |
| 2.1.54 | 18 / 9 | |
| 2.1.53 | 18 / 9 | |
| 2.1.52 | 18 / 9 | |
| 2.1.51 | 18 / 9 | |
| 2.1.50 | 18 / 9 | |
| 2.1.49 | 18 / 9 | |
| 2.1.48 | 18 / 9 | |
| 2.1.47 | 18 / 9 | |
| 2.1.46 | 18 / 9 | |
| 2.1.45 | 18 / 9 | |
| 2.1.44 | 18 / 9 | |
| 2.1.43 | 18 / 9 | |
| 2.1.42 | 18 / 9 | |
| 2.1.41 | 18 / 9 | |
| 2.1.40 | 18 / 9 | |
| 2.1.39 | 18 / 9 | |
| 2.1.38 | 18 / 9 | |
| 2.1.37 | 18 / 9 | |
| 2.1.36 | 18 / 9 | |
| 2.1.35 | 18 / 9 | |
| 2.1.34 | 18 / 9 | |
| 2.1.33 | 18 / 9 | |
| 2.1.32 | 18 / 9 | |
| 2.1.31 | 18 / 9 | |
| 2.1.30 | 18 / 9 | |
| 2.1.29 | 18 / 9 | |
| 2.1.28 | 18 / 9 | |
| 2.1.27 | 18 / 9 | |
| 2.1.26 | 18 / 9 | |
| 2.1.25 | 18 / 9 | |
| 2.1.24 | 18 / 9 | |
| 2.1.23 | 18 / 9 | |
| 2.1.22 | 18 / 9 | |
| 2.1.21 | 18 / 9 | |
| 2.1.20 | 18 / 9 | |
| 2.1.19 | 18 / 9 | |
| 2.1.18 | 18 / 9 | |
| 2.1.17 | 18 / 9 | |
| 2.1.16 | 18 / 9 | |
| 2.1.15 | 18 / 9 | |
| 2.1.14 | 18 / 9 | |
| 2.1.13 | 18 / 9 | |
| 2.1.11 | 18 / 9 | |
| 2.1.10 | 18 / 9 | |
| 2.1.9 | 18 / 9 | |
| 2.1.8 | 18 / 9 | |
| 2.1.7 | 18 / 9 | |
| 2.1.6 | 18 / 9 | |
| 2.1.5 | 18 / 9 | |
| 2.1.4 | 18 / 9 | |
| 2.1.3 | 18 / 9 | |
| 2.1.2 | 18 / 9 | |
| 2.1.1 | 18 / 9 | |
| 2.1.0 | 18 / 9 | |
| 2.0.174 | 18 / 9 | |
| 2.0.173 | 18 / 9 | |
| 2.0.172 | 18 / 9 | |
| 2.0.171 | 18 / 9 | |
| 2.0.170 | 18 / 9 | |
| 2.0.169 | 18 / 9 | |
| 2.0.168 | 18 / 9 | |
| 2.0.167 | 18 / 9 | |
| 2.0.166 | 18 / 9 | |
| 2.0.165 | 18 / 9 | |
| 2.0.164 | 18 / 9 | |
| 2.0.163 | 18 / 9 | |
| 2.0.162 | 18 / 9 | |
| 2.0.161 | 18 / 9 | |
| 2.0.160 | 18 / 9 | |
| 2.0.159 | 18 / 9 | |
| 2.0.158 | 18 / 9 | |
| 2.0.157 | 18 / 9 | |
| 2.0.156 | 18 / 9 | |
| 2.0.155 | 18 / 9 | |
| 2.0.154 | 18 / 9 | |
| 2.0.153 | 18 / 9 | |
| 2.0.152 | 18 / 9 | |
| 2.0.151 | 18 / 9 | |
| 2.0.150 | 18 / 9 | |
| 2.0.149 | 18 / 9 | |
| 2.0.148 | 18 / 9 | |
| 2.0.147 | 18 / 9 | |
| 2.0.146 | 18 / 9 | |
| 2.0.145 | 18 / 9 | |
| 2.0.144 | 18 / 9 | |
| 2.0.143 | 18 / 9 | |
| 2.0.142 | 18 / 9 | |
| 2.0.141 | 18 / 9 | |
| 2.0.140 | 18 / 9 |
v2.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.170
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.168
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.154
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.153
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.