@finos/legend-extension-assortment Apache-2.0 51 versions

@finos/legend-extension-assortment

npm Repository Homepage

An assortment of Legend extensions

51

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-extension

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	2026/04/29
phantom-deps	phantom-dep:serializr	AI (phantom-deps): serializr referenced in config files per analyzer note; stable false positive for this monorepo package.	ai	2026/04/29
phantom-deps	phantom-dep:@types/react	AI (phantom-deps): Framework-scoped type package; loaded by convention, not direct import.	ai	2026/04/29
phantom-deps	phantom-dep:mobx-react-lite	AI (phantom-deps): Config-referenced framework dep; stable false positive for this package.	ai	2026/04/29
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	2026/04/29

Versions (showing 51 of 140)

View all versions

Version	Deps	Published
0.0.448	11 / 9	2026-06-05
0.0.447	11 / 9	2026-06-04
0.0.446	11 / 9	2026-06-03
0.0.445	11 / 9	2026-06-03
0.0.444	11 / 9	2026-06-01
0.0.443	11 / 9	2026-05-26
0.0.442	11 / 9	2026-05-20
0.0.441	11 / 9	2026-05-18
0.0.440	11 / 9	2026-05-11
0.0.439	11 / 9	2026-05-11
0.0.438	11 / 9	2026-05-07
0.0.437	11 / 9	2026-05-06
0.0.436	11 / 9	2026-05-05
0.0.435	11 / 9	2026-05-01
0.0.434	11 / 9	2026-04-29
0.0.433	11 / 9	2026-04-27
0.0.429	11 / 9	2026-03-31
0.0.428	11 / 9	2026-03-24
0.0.427	11 / 9	2026-03-24
0.0.426	11 / 9	2026-03-20
0.0.424	11 / 9	2026-03-17
0.0.422	11 / 9	2026-03-10
0.0.421	11 / 9	2026-03-09
0.0.420	11 / 9	2026-03-07
0.0.419	11 / 9	2026-03-06
0.0.418	11 / 9	2026-03-04
0.0.416	11 / 9	2026-02-26
0.0.415	11 / 9	2026-02-25
0.0.414	11 / 9	2026-02-23
0.0.413	11 / 9	2026-02-19
0.0.412	11 / 9	2026-02-14
0.0.410	11 / 9	2026-02-11
0.0.406	11 / 9	2026-01-27
0.0.403	11 / 9	2026-01-20
0.0.402	11 / 9	2026-01-16
0.0.400	11 / 9	2026-01-07
0.0.399	11 / 9	2026-01-06
0.0.398	11 / 9	2025-12-19
0.0.396	11 / 9	2025-12-15
0.0.395	11 / 9	2025-12-11
0.0.394	11 / 9	2025-12-11
0.0.393	11 / 9	2025-12-11
0.0.392	11 / 9	2025-12-10
0.0.390	11 / 9	2025-12-04
0.0.388	11 / 9	2025-12-03
0.0.387	11 / 9	2025-12-02
0.0.385	11 / 9	2025-11-19
0.0.380	11 / 9	2025-11-05
0.0.379	11 / 9	2025-11-05
0.0.375	11 / 9	2025-10-30
0.0.374	11 / 9	2025-10-28

v0.0.448

1 finding

LOW No provenance attestation provenance

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

v0.0.447

1 finding

LOW No provenance attestation provenance

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

v0.0.446

1 finding

LOW No provenance attestation provenance

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

v0.0.445

1 finding

LOW No provenance attestation provenance

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

v0.0.444

1 finding

LOW No provenance attestation provenance

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

v0.0.443

1 finding

LOW No provenance attestation provenance

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

v0.0.442

1 finding

LOW No provenance attestation provenance

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

v0.0.441

1 finding

LOW No provenance attestation provenance

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

v0.0.440

1 finding

LOW No provenance attestation provenance

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

v0.0.439

1 finding

LOW No provenance attestation provenance

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

v0.0.438

1 finding

LOW No provenance attestation provenance

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

v0.0.437

1 finding

LOW No provenance attestation provenance

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

v0.0.436

1 finding

LOW No provenance attestation provenance

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

v0.0.435

1 finding

LOW No provenance attestation provenance

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

v0.0.434

1 finding

LOW No provenance attestation provenance

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

v0.0.429

1 finding

LOW No provenance attestation provenance

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

v0.0.428

1 finding

LOW No provenance attestation provenance

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

v0.0.427

1 finding

LOW No provenance attestation provenance

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

v0.0.426

1 finding

LOW No provenance attestation provenance

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

v0.0.424

1 finding

LOW No provenance attestation provenance

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

v0.0.422

1 finding

LOW No provenance attestation provenance

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

v0.0.421

1 finding

LOW No provenance attestation provenance

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

v0.0.420

1 finding

LOW No provenance attestation provenance

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

v0.0.419

1 finding

LOW No provenance attestation provenance

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

v0.0.418

1 finding

LOW No provenance attestation provenance

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

v0.0.416

1 finding

LOW No provenance attestation provenance

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

v0.0.415

1 finding

LOW No provenance attestation provenance

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

v0.0.414

1 finding

LOW No provenance attestation provenance

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

v0.0.413

1 finding

LOW No provenance attestation provenance

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

v0.0.412

1 finding

LOW No provenance attestation provenance

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

v0.0.410

1 finding

LOW No provenance attestation provenance

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

v0.0.406

1 finding

LOW No provenance attestation provenance

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

v0.0.403

1 finding

LOW No provenance attestation provenance

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

v0.0.402

1 finding

LOW No provenance attestation provenance

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

v0.0.400

1 finding

LOW No provenance attestation provenance

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

v0.0.399

1 finding

LOW No provenance attestation provenance

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

v0.0.398

1 finding

LOW No provenance attestation provenance

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

v0.0.396

1 finding

LOW No provenance attestation provenance

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

v0.0.395

1 finding

LOW No provenance attestation provenance

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

v0.0.394

1 finding

LOW No provenance attestation provenance

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

v0.0.393

1 finding

LOW No provenance attestation provenance

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

v0.0.392

1 finding

LOW No provenance attestation provenance

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

v0.0.390

1 finding

LOW No provenance attestation provenance

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

v0.0.388

1 finding

LOW No provenance attestation provenance

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

v0.0.387

1 finding

LOW No provenance attestation provenance

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

v0.0.385

1 finding

LOW No provenance attestation provenance

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

v0.0.380

1 finding

LOW No provenance attestation provenance

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

v0.0.379

1 finding

LOW No provenance attestation provenance

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

v0.0.375

1 finding

LOW No provenance attestation provenance

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

v0.0.374

1 finding

LOW No provenance attestation provenance

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