@finos/legend-server-showcase
Legend Showcase 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mobx | AI (phantom-deps): mobx is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): yaml is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): fastify is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 80 of 80)
| Version | Deps | Published |
|---|---|---|
| 0.2.67 | 5 / 8 | |
| 0.2.66 | 5 / 8 | |
| 0.2.65 | 5 / 8 | |
| 0.2.64 | 5 / 8 | |
| 0.2.63 | 5 / 8 | |
| 0.2.62 | 5 / 8 | |
| 0.2.61 | 5 / 8 | |
| 0.2.60 | 5 / 8 | |
| 0.2.59 | 5 / 8 | |
| 0.2.58 | 5 / 8 | |
| 0.2.57 | 5 / 8 | |
| 0.2.56 | 5 / 8 | |
| 0.2.55 | 5 / 8 | |
| 0.2.54 | 5 / 8 | |
| 0.2.53 | 5 / 8 | |
| 0.2.52 | 5 / 8 | |
| 0.2.51 | 5 / 8 | |
| 0.2.50 | 5 / 8 | |
| 0.2.49 | 5 / 8 | |
| 0.2.48 | 5 / 8 | |
| 0.2.47 | 5 / 8 | |
| 0.2.46 | 5 / 8 | |
| 0.2.45 | 5 / 8 | |
| 0.2.44 | 5 / 8 | |
| 0.2.43 | 5 / 8 | |
| 0.2.42 | 5 / 8 | |
| 0.2.41 | 5 / 8 | |
| 0.2.40 | 5 / 8 | |
| 0.2.39 | 5 / 8 | |
| 0.2.38 | 5 / 8 | |
| 0.2.37 | 5 / 8 | |
| 0.2.36 | 5 / 8 | |
| 0.2.35 | 5 / 8 | |
| 0.2.34 | 5 / 8 | |
| 0.2.33 | 5 / 8 | |
| 0.2.32 | 5 / 8 | |
| 0.2.31 | 5 / 8 | |
| 0.2.30 | 5 / 8 | |
| 0.2.29 | 5 / 8 | |
| 0.2.28 | 5 / 8 | |
| 0.2.27 | 5 / 8 | |
| 0.2.26 | 5 / 8 | |
| 0.2.25 | 5 / 8 | |
| 0.2.24 | 5 / 8 | |
| 0.2.23 | 5 / 8 | |
| 0.2.22 | 5 / 8 | |
| 0.2.21 | 5 / 8 | |
| 0.2.20 | 5 / 8 | |
| 0.2.19 | 5 / 8 | |
| 0.2.18 | 5 / 8 | |
| 0.2.17 | 5 / 8 | |
| 0.2.16 | 5 / 8 | |
| 0.2.15 | 5 / 8 | |
| 0.2.14 | 5 / 8 | |
| 0.2.13 | 5 / 8 | |
| 0.2.12 | 5 / 8 | |
| 0.2.11 | 5 / 8 | |
| 0.2.10 | 5 / 8 | |
| 0.2.9 | 5 / 8 | |
| 0.2.8 | 5 / 8 | |
| 0.2.7 | 5 / 8 | |
| 0.2.6 | 5 / 8 | |
| 0.2.5 | 5 / 8 | |
| 0.2.4 | 5 / 8 | |
| 0.2.3 | 5 / 8 | |
| 0.2.2 | 5 / 8 | |
| 0.2.1 | 5 / 8 | |
| 0.2.0 | 5 / 8 | |
| 0.1.0 | 5 / 8 | |
| 0.0.11 | 5 / 8 | |
| 0.0.10 | 5 / 8 | |
| 0.0.9 | 5 / 8 | |
| 0.0.8 | 5 / 8 | |
| 0.0.7 | 5 / 8 | |
| 0.0.6 | 5 / 8 | |
| 0.0.5 | 5 / 8 | |
| 0.0.4 | 5 / 8 | |
| 0.0.3 | 5 / 8 | |
| 0.0.2 | 5 / 8 | |
| 0.0.1 | 5 / 8 |
v0.2.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.