@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 — 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:@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 64 of 165)
| Version | Deps | Published |
|---|---|---|
| 6.0.370 | 13 / 9 | |
| 6.0.369 | 13 / 9 | |
| 6.0.368 | 13 / 9 | |
| 6.0.367 | 13 / 9 | |
| 6.0.366 | 13 / 9 | |
| 6.0.365 | 13 / 9 | |
| 6.0.364 | 13 / 9 | |
| 6.0.363 | 13 / 9 | |
| 6.0.362 | 13 / 9 | |
| 6.0.361 | 13 / 9 | |
| 6.0.360 | 13 / 9 | |
| 6.0.359 | 13 / 9 | |
| 6.0.358 | 13 / 9 | |
| 6.0.357 | 13 / 9 | |
| 6.0.356 | 13 / 9 | |
| 6.0.355 | 13 / 9 | |
| 6.0.354 | 13 / 9 | |
| 6.0.353 | 13 / 9 | |
| 6.0.352 | 13 / 9 | |
| 6.0.351 | 13 / 9 | |
| 6.0.350 | 13 / 9 | |
| 6.0.349 | 13 / 9 | |
| 6.0.348 | 13 / 9 | |
| 6.0.347 | 13 / 9 | |
| 6.0.346 | 13 / 9 | |
| 6.0.345 | 13 / 9 | |
| 6.0.344 | 13 / 9 | |
| 6.0.343 | 13 / 9 | |
| 6.0.342 | 13 / 9 | |
| 6.0.341 | 13 / 9 | |
| 6.0.340 | 13 / 9 | |
| 6.0.339 | 13 / 9 | |
| 6.0.338 | 13 / 9 | |
| 6.0.337 | 13 / 9 | |
| 6.0.336 | 13 / 9 | |
| 6.0.335 | 13 / 9 | |
| 6.0.334 | 13 / 9 | |
| 6.0.333 | 13 / 9 | |
| 6.0.332 | 13 / 9 | |
| 6.0.331 | 13 / 9 | |
| 6.0.330 | 13 / 9 | |
| 6.0.329 | 13 / 9 | |
| 6.0.328 | 13 / 9 | |
| 6.0.327 | 13 / 9 | |
| 6.0.326 | 13 / 9 | |
| 6.0.325 | 13 / 9 | |
| 6.0.324 | 13 / 9 | |
| 6.0.323 | 13 / 9 | |
| 6.0.322 | 13 / 9 | |
| 6.0.321 | 13 / 9 | |
| 6.0.320 | 13 / 9 | |
| 6.0.319 | 13 / 9 | |
| 6.0.318 | 13 / 9 | |
| 6.0.317 | 13 / 9 | |
| 6.0.316 | 13 / 9 | |
| 6.0.315 | 13 / 9 | |
| 6.0.314 | 13 / 9 | |
| 6.0.313 | 13 / 9 | |
| 6.0.312 | 13 / 9 | |
| 6.0.311 | 13 / 9 | |
| 6.0.310 | 13 / 9 | |
| 6.0.309 | 13 / 9 | |
| 6.0.308 | 13 / 9 | |
| 6.0.307 | 13 / 9 |
v6.0.370
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.369
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.368
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.367
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.366
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.365
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.364
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.363
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.362
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.361
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.360
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.359
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.358
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.357
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.356
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.355
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.354
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.353
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.352
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.351
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.350
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.349
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.348
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.347
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.346
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.345
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.344
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.343
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.342
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.341
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.340
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.339
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.338
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.337
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.336
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.335
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.334
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.333
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.332
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.331
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.330
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.329
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.328
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.327
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.326
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.325
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.324
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.323
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.322
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.321
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.320
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.319
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.318
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.317
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.316
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.315
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.314
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.313
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.312
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.311
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.309
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.307
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.