@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, so a manually published version cannot be tied back to a reviewed commit.
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 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 32.6.22 | 4 / 9 | |
| 32.6.21 | 4 / 9 | |
| 32.6.20 | 4 / 9 | |
| 32.6.19 | 4 / 9 | |
| 32.6.18 | 4 / 9 | |
| 32.6.17 | 4 / 9 | |
| 32.6.16 | 4 / 9 | |
| 32.6.15 | 4 / 9 | |
| 32.6.14 | 4 / 9 | |
| 32.6.13 | 4 / 9 | |
| 32.6.12 | 4 / 9 | |
| 32.6.11 | 4 / 9 | |
| 32.6.10 | 4 / 9 | |
| 32.6.9 | 4 / 9 | |
| 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 | |
| 32.4.1 | 4 / 9 | |
| 32.4.0 | 4 / 9 | |
| 32.3.39 | 4 / 9 | |
| 32.3.38 | 4 / 9 | |
| 32.3.37 | 4 / 9 | |
| 32.3.36 | 4 / 9 | |
| 32.3.35 | 4 / 9 | |
| 32.3.34 | 4 / 9 | |
| 32.3.33 | 4 / 9 | |
| 32.3.32 | 4 / 9 | |
| 32.3.31 | 4 / 9 | |
| 32.3.29 | 4 / 9 | |
| 32.3.28 | 4 / 9 | |
| 32.3.27 | 4 / 9 | |
| 32.3.26 | 4 / 9 | |
| 32.3.25 | 4 / 9 | |
| 32.3.24 | 4 / 9 | |
| 32.3.23 | 4 / 9 | |
| 32.3.22 | 4 / 9 | |
| 32.3.21 | 4 / 9 | |
| 32.3.20 | 4 / 9 | |
| 32.3.19 | 4 / 9 | |
| 32.3.18 | 4 / 9 | |
| 32.3.17 | 4 / 9 | |
| 32.3.16 | 4 / 9 | |
| 32.3.15 | 4 / 9 | |
| 32.3.14 | 4 / 9 | |
| 32.3.13 | 4 / 9 | |
| 32.3.12 | 4 / 9 | |
| 32.3.11 | 4 / 9 | |
| 32.3.10 | 4 / 9 |
v32.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v32.3.11
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.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.