@finos/legend-extension-dsl-text
Legend extension for Text DSL
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@finos/legend-art | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-lego | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-graph | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-shared | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-storage | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-application | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-code-editor | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@finos/legend-application-studio | AI (dependencies): Sibling FINOS/Legend package; expected dependency for this org's ecosystem. | ai | |
| dependencies | unvetted-dep:serializr | AI (dependencies): serializr is a well-known MobX serialization library; standard dep for Legend packages. | ai | |
| phantom-deps | phantom-dep:@finos/legend-storage | AI (phantom-deps): Same-org sibling; phantom-dep heuristic unreliable for transitive org deps. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only package; not directly imported at runtime by convention. | ai |
Versions (showing 81 of 481)
| Version | Deps | Published |
|---|---|---|
| 6.0.80 | 12 / 9 | |
| 6.0.79 | 12 / 9 | |
| 6.0.78 | 12 / 9 | |
| 6.0.77 | 12 / 9 | |
| 6.0.76 | 12 / 9 | |
| 6.0.75 | 12 / 9 | |
| 6.0.74 | 12 / 9 | |
| 6.0.73 | 12 / 9 | |
| 6.0.72 | 12 / 9 | |
| 6.0.71 | 12 / 9 | |
| 6.0.70 | 12 / 9 | |
| 6.0.69 | 12 / 9 | |
| 6.0.68 | 12 / 9 | |
| 6.0.67 | 12 / 9 | |
| 6.0.66 | 12 / 9 | |
| 6.0.65 | 12 / 9 | |
| 6.0.64 | 12 / 9 | |
| 6.0.63 | 12 / 9 | |
| 6.0.62 | 12 / 9 | |
| 6.0.61 | 12 / 9 | |
| 6.0.60 | 12 / 9 | |
| 6.0.59 | 12 / 9 | |
| 6.0.58 | 12 / 9 | |
| 6.0.57 | 12 / 9 | |
| 6.0.56 | 12 / 9 | |
| 6.0.55 | 12 / 9 | |
| 6.0.54 | 12 / 9 | |
| 6.0.53 | 12 / 9 | |
| 6.0.52 | 12 / 9 | |
| 6.0.51 | 12 / 9 | |
| 6.0.50 | 12 / 9 | |
| 6.0.49 | 12 / 9 | |
| 6.0.48 | 12 / 9 | |
| 6.0.47 | 12 / 9 | |
| 6.0.46 | 12 / 9 | |
| 6.0.45 | 12 / 9 | |
| 6.0.44 | 12 / 9 | |
| 6.0.43 | 12 / 9 | |
| 6.0.42 | 12 / 9 | |
| 6.0.41 | 12 / 9 | |
| 6.0.40 | 12 / 9 | |
| 6.0.39 | 12 / 9 | |
| 6.0.38 | 12 / 9 | |
| 6.0.37 | 12 / 9 | |
| 6.0.36 | 12 / 9 | |
| 6.0.35 | 12 / 9 | |
| 6.0.34 | 12 / 9 | |
| 6.0.33 | 12 / 9 | |
| 6.0.32 | 12 / 9 | |
| 6.0.31 | 12 / 9 | |
| 6.0.30 | 12 / 9 | |
| 6.0.29 | 12 / 9 | |
| 6.0.28 | 12 / 9 | |
| 6.0.27 | 12 / 9 | |
| 6.0.26 | 12 / 9 | |
| 6.0.25 | 12 / 9 | |
| 6.0.24 | 12 / 9 | |
| 6.0.23 | 12 / 9 | |
| 6.0.22 | 12 / 9 | |
| 6.0.21 | 12 / 9 | |
| 6.0.20 | 12 / 9 | |
| 6.0.19 | 12 / 9 | |
| 6.0.18 | 12 / 9 | |
| 6.0.17 | 12 / 9 | |
| 6.0.16 | 12 / 9 | |
| 6.0.15 | 12 / 9 | |
| 6.0.14 | 12 / 9 | |
| 6.0.13 | 12 / 9 | |
| 6.0.12 | 12 / 9 | |
| 6.0.11 | 12 / 9 | |
| 6.0.10 | 12 / 9 | |
| 6.0.9 | 12 / 9 | |
| 6.0.8 | 12 / 9 | |
| 6.0.7 | 12 / 9 | |
| 6.0.6 | 12 / 9 | |
| 6.0.5 | 12 / 9 | |
| 6.0.4 | 12 / 9 | |
| 6.0.3 | 12 / 9 | |
| 6.0.2 | 12 / 9 | |
| 6.0.1 | 12 / 9 | |
| 6.0.0 | 12 / 9 |
v6.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.