@finos/legend-extension-assortment
An assortment of Legend extensions
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): MobX is a peer/framework dep used via config in Legend monorepo; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:serializr | AI (phantom-deps): serializr referenced in config files per analyzer note; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped type package; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:mobx-react-lite | AI (phantom-deps): Config-referenced framework dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@finos/legend-application | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for Legend monorepo packages. | ai |
Versions (showing 42 of 143)
| Version | Deps | Published |
|---|---|---|
| 0.0.326 | 11 / 9 | |
| 0.0.325 | 11 / 9 | |
| 0.0.324 | 11 / 9 | |
| 0.0.323 | 11 / 9 | |
| 0.0.322 | 11 / 9 | |
| 0.0.321 | 11 / 9 | |
| 0.0.320 | 11 / 9 | |
| 0.0.319 | 11 / 9 | |
| 0.0.318 | 11 / 9 | |
| 0.0.317 | 11 / 9 | |
| 0.0.316 | 11 / 9 | |
| 0.0.315 | 11 / 9 | |
| 0.0.314 | 11 / 9 | |
| 0.0.313 | 11 / 9 | |
| 0.0.312 | 11 / 9 | |
| 0.0.311 | 11 / 9 | |
| 0.0.310 | 11 / 9 | |
| 0.0.309 | 11 / 9 | |
| 0.0.308 | 11 / 9 | |
| 0.0.307 | 11 / 9 | |
| 0.0.306 | 11 / 9 | |
| 0.0.305 | 11 / 9 | |
| 0.0.304 | 11 / 9 | |
| 0.0.303 | 11 / 9 | |
| 0.0.302 | 11 / 9 | |
| 0.0.301 | 11 / 9 | |
| 0.0.300 | 11 / 9 | |
| 0.0.299 | 11 / 9 | |
| 0.0.298 | 11 / 9 | |
| 0.0.297 | 11 / 9 | |
| 0.0.296 | 11 / 9 | |
| 0.0.295 | 11 / 9 | |
| 0.0.294 | 11 / 9 | |
| 0.0.293 | 11 / 9 | |
| 0.0.292 | 11 / 9 | |
| 0.0.291 | 11 / 9 | |
| 0.0.290 | 11 / 9 | |
| 0.0.289 | 11 / 9 | |
| 0.0.288 | 11 / 9 | |
| 0.0.287 | 11 / 9 | |
| 0.0.286 | 11 / 9 | |
| 0.0.285 | 11 / 9 |
v0.0.326
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.325
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.324
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.323
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.322
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.321
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.320
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.319
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.318
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.317
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.316
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.315
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.313
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.312
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.311
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.310
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.309
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.308
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.307
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.306
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.305
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.304
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.303
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.302
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.301
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.300
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.299
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.298
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.297
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.296
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.295
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.294
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.293
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.291
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.290
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.289
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.288
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.287
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.286
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.285
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.