@finos/legend-graph
Legend graph and graph manager
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:serializr | AI (dependencies): serializr is a well-known serialization library; stable long-term dependency of this package. | ai | |
| provenance | no-provenance | AI (provenance): FINOS org package; no provenance is consistent across all 441 versions, not a new concern. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 32.6.8 | 4 / 9 | |
| 32.6.7 | 4 / 9 | |
| 32.6.6 | 4 / 9 | |
| 32.6.5 | 4 / 9 | |
| 32.6.4 | 4 / 9 | |
| 32.6.3 | 4 / 9 | |
| 32.6.2 | 4 / 9 | |
| 32.6.1 | 4 / 9 | |
| 32.6.0 | 4 / 9 | |
| 32.5.3 | 4 / 9 | |
| 32.5.2 | 4 / 9 | |
| 32.5.1 | 4 / 9 | |
| 32.5.0 | 4 / 9 | |
| 32.4.3 | 4 / 9 | |
| 32.4.2 | 4 / 9 |
v32.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v32.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.