← Home

@finos/legend-extension-dsl-diagram-studio

Legend extension for Diagram DSL Studio

32
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-extensiondsldsl-diagram-studio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:serializr AI (dependencies): serializr is a well-known, widely-used serialization library; stable false positive for this package. ai
provenance no-provenance AI (provenance): FINOS org package published via standard npm; lack of Sigstore attestation is common and not a risk signal here. ai
dependencies unvetted-dep:@finos/legend-shared AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@finos/legend-storage AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@finos/legend-application AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@finos/legend-code-editor AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@finos/legend-application-studio AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@finos/legend-art AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): react-dom is a standard peer/runtime dep in React packages; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:serializr AI (phantom-deps): Declared in package.json; phantom-dep heuristic false positive for this 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:@finos/legend-storage AI (phantom-deps): Same-org sibling; phantom-dep heuristic false positive. ai
dependencies unvetted-dep:@finos/legend-extension-dsl-diagram AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai
dependencies unvetted-dep:@finos/legend-graph AI (dependencies): Same-org FINOS monorepo sibling; stable pattern across all versions. ai

Versions (showing 32 of 32)

Version Deps Published
0.0.62 15 / 11
0.0.61 15 / 11
0.0.60 15 / 11
0.0.59 15 / 11
0.0.58 15 / 11
0.0.57 15 / 11
0.0.56 15 / 11
0.0.55 15 / 11
0.0.54 15 / 11
0.0.53 15 / 11
0.0.52 15 / 11
0.0.51 15 / 11
0.0.50 15 / 11
0.0.49 15 / 11
0.0.48 15 / 11
0.0.47 15 / 11
0.0.44 15 / 11
0.0.43 15 / 11
0.0.41 15 / 11
0.0.36 15 / 11
0.0.35 15 / 11
0.0.31 15 / 11
0.0.27 15 / 11
0.0.24 15 / 11
0.0.22 15 / 11
0.0.20 15 / 11
0.0.19 15 / 11
0.0.18 15 / 11
0.0.17 15 / 11
0.0.7 15 / 11
0.0.6 15 / 11
0.0.2 15 / 11

v0.0.62

1 finding
INFO No provenance attestation provenance

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

v0.0.61

1 finding
INFO No provenance attestation provenance

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

v0.0.60

1 finding
INFO No provenance attestation provenance

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

v0.0.59

1 finding
INFO No provenance attestation provenance

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

v0.0.58

1 finding
INFO No provenance attestation provenance

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

v0.0.57

1 finding
INFO No provenance attestation provenance

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

v0.0.56

1 finding
INFO No provenance attestation provenance

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

v0.0.55

1 finding
INFO No provenance attestation provenance

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

v0.0.54

1 finding
INFO No provenance attestation provenance

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

v0.0.53

1 finding
INFO No provenance attestation provenance

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

v0.0.52

1 finding
INFO No provenance attestation provenance

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

v0.0.51

1 finding
INFO No provenance attestation provenance

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

v0.0.50

1 finding
INFO No provenance attestation provenance

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

v0.0.49

1 finding
INFO No provenance attestation provenance

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

v0.0.48

1 finding
INFO No provenance attestation provenance

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

v0.0.44

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.43

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.41

1 finding
INFO No provenance attestation provenance

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

v0.0.36

1 finding
INFO No provenance attestation provenance

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

v0.0.35

1 finding
INFO No provenance attestation provenance

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

v0.0.31

1 finding
INFO No provenance attestation provenance

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

v0.0.27

1 finding
INFO No provenance attestation provenance

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

v0.0.24

1 finding
INFO No provenance attestation provenance

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

v0.0.22

1 finding
INFO No provenance attestation provenance

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

v0.0.20

1 finding
INFO No provenance attestation provenance

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

v0.0.19

1 finding
INFO No provenance attestation provenance

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

v0.0.18

1 finding
INFO No provenance attestation provenance

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

v0.0.17

1 finding
INFO No provenance attestation provenance

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

v0.0.7

1 finding
INFO No provenance attestation provenance

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

v0.0.6

1 finding
INFO No provenance attestation provenance

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

v0.0.2

1 finding
INFO No provenance attestation provenance

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