@finos/legend-server-sdlc
Legend SDLC server client
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): FINOS legend-studio monorepo does not publish Sigstore provenance; consistent across all versions. | ai |
Versions (showing 100 of 118)
| Version | Deps | Published |
|---|---|---|
| 5.4.6 | 4 / 8 | |
| 5.4.5 | 4 / 8 | |
| 5.4.4 | 4 / 8 | |
| 5.4.3 | 4 / 8 | |
| 5.4.2 | 4 / 8 | |
| 5.4.1 | 4 / 8 | |
| 5.4.0 | 4 / 8 | |
| 5.3.74 | 4 / 8 | |
| 5.3.73 | 4 / 8 | |
| 5.3.71 | 4 / 8 | |
| 5.3.70 | 4 / 8 | |
| 5.3.69 | 4 / 8 | |
| 5.3.68 | 4 / 8 | |
| 5.3.67 | 4 / 8 | |
| 5.3.66 | 4 / 8 | |
| 5.3.65 | 4 / 8 | |
| 5.3.64 | 4 / 8 | |
| 5.3.63 | 4 / 8 | |
| 5.3.62 | 4 / 8 | |
| 5.3.61 | 4 / 8 | |
| 5.3.60 | 4 / 8 | |
| 5.3.59 | 4 / 8 | |
| 5.3.58 | 4 / 8 | |
| 5.3.57 | 4 / 8 | |
| 5.3.56 | 4 / 8 | |
| 5.3.55 | 4 / 8 | |
| 5.3.54 | 4 / 8 | |
| 5.3.53 | 4 / 8 | |
| 5.3.52 | 4 / 8 | |
| 5.3.51 | 4 / 8 | |
| 5.3.50 | 4 / 8 | |
| 5.3.49 | 4 / 8 | |
| 5.3.48 | 4 / 8 | |
| 5.3.47 | 4 / 8 | |
| 5.3.46 | 4 / 8 | |
| 5.3.45 | 4 / 8 | |
| 5.3.44 | 4 / 8 | |
| 5.3.43 | 4 / 8 | |
| 5.3.42 | 4 / 8 | |
| 5.3.41 | 4 / 8 | |
| 5.3.40 | 4 / 8 | |
| 5.3.39 | 4 / 8 | |
| 5.3.38 | 4 / 8 | |
| 5.3.37 | 4 / 8 | |
| 5.3.36 | 4 / 8 | |
| 5.3.35 | 4 / 8 | |
| 5.3.34 | 4 / 8 | |
| 5.3.33 | 4 / 8 | |
| 5.3.32 | 4 / 8 | |
| 5.3.31 | 4 / 8 | |
| 5.3.30 | 4 / 8 | |
| 5.3.29 | 4 / 8 | |
| 5.3.28 | 4 / 8 | |
| 5.3.27 | 4 / 8 | |
| 5.3.26 | 4 / 8 | |
| 5.3.25 | 4 / 8 | |
| 5.3.24 | 4 / 8 | |
| 5.3.23 | 4 / 8 | |
| 5.3.22 | 4 / 8 | |
| 5.3.21 | 4 / 8 | |
| 5.3.20 | 4 / 8 | |
| 5.3.19 | 4 / 8 | |
| 5.3.18 | 4 / 8 | |
| 5.3.17 | 4 / 8 | |
| 5.3.16 | 4 / 8 | |
| 5.3.15 | 4 / 8 | |
| 5.3.14 | 4 / 8 | |
| 5.3.13 | 4 / 8 | |
| 5.3.12 | 4 / 8 | |
| 5.3.11 | 4 / 8 | |
| 5.3.10 | 4 / 8 | |
| 5.3.9 | 4 / 8 | |
| 5.3.8 | 4 / 8 | |
| 5.3.7 | 4 / 8 | |
| 5.3.6 | 4 / 8 | |
| 5.3.5 | 4 / 8 | |
| 5.3.4 | 4 / 8 | |
| 5.3.3 | 4 / 8 | |
| 5.3.2 | 4 / 8 | |
| 5.3.1 | 4 / 8 | |
| 5.3.0 | 4 / 8 | |
| 5.2.3 | 4 / 8 | |
| 5.2.2 | 4 / 8 | |
| 5.2.1 | 4 / 8 | |
| 5.2.0 | 4 / 8 | |
| 5.1.3 | 4 / 8 | |
| 5.1.2 | 4 / 8 | |
| 5.1.1 | 4 / 8 | |
| 5.1.0 | 4 / 8 | |
| 5.0.28 | 4 / 8 | |
| 5.0.27 | 4 / 8 | |
| 5.0.26 | 4 / 8 | |
| 5.0.25 | 4 / 8 | |
| 5.0.24 | 4 / 8 | |
| 5.0.23 | 4 / 8 | |
| 5.0.22 | 4 / 8 | |
| 5.0.21 | 4 / 8 | |
| 5.0.20 | 4 / 8 | |
| 5.0.19 | 4 / 8 | |
| 5.0.18 | 4 / 8 |
v5.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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.
v5.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.
v5.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.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.
v5.3.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.
v5.3.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.
v5.3.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.2.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.1.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.
v5.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.