@finos/legend-application
Legend application core
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): Established FINOS org package; lack of Sigstore provenance is consistent across all prior versions. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/framework dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only declaration; framework-scoped, stable false positive. | ai | |
| phantom-deps | phantom-dep:oidc-client-ts | AI (phantom-deps): Transitive peer of react-oidc-context; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only declaration; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/react-router-dom | AI (phantom-deps): Type-only declaration; stable false positive. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 16.0.117 | 23 / 11 | |
| 16.0.116 | 23 / 11 | |
| 16.0.115 | 23 / 11 | |
| 16.0.114 | 23 / 11 | |
| 16.0.113 | 23 / 11 | |
| 16.0.112 | 23 / 11 | |
| 16.0.111 | 23 / 11 | |
| 16.0.110 | 23 / 11 | |
| 16.0.109 | 23 / 11 | |
| 16.0.108 | 23 / 11 | |
| 16.0.107 | 23 / 11 | |
| 16.0.106 | 23 / 11 | |
| 16.0.105 | 23 / 11 | |
| 16.0.104 | 23 / 11 | |
| 16.0.103 | 23 / 11 | |
| 16.0.102 | 22 / 11 | |
| 16.0.101 | 22 / 11 | |
| 16.0.100 | 22 / 11 | |
| 16.0.99 | 22 / 11 | |
| 16.0.98 | 20 / 11 | |
| 16.0.97 | 20 / 11 | |
| 16.0.96 | 20 / 11 | |
| 16.0.95 | 20 / 11 | |
| 16.0.93 | 20 / 11 | |
| 16.0.92 | 20 / 11 | |
| 16.0.91 | 20 / 11 | |
| 16.0.90 | 20 / 9 | |
| 16.0.89 | 20 / 9 | |
| 16.0.88 | 20 / 9 | |
| 16.0.87 | 20 / 9 | |
| 16.0.86 | 20 / 9 | |
| 16.0.85 | 20 / 9 | |
| 16.0.84 | 20 / 9 | |
| 16.0.83 | 20 / 9 | |
| 16.0.82 | 20 / 9 | |
| 16.0.81 | 20 / 9 | |
| 16.0.80 | 20 / 9 | |
| 16.0.79 | 20 / 9 | |
| 16.0.78 | 20 / 9 | |
| 16.0.77 | 20 / 9 | |
| 16.0.76 | 20 / 9 | |
| 16.0.75 | 20 / 9 | |
| 16.0.74 | 20 / 9 | |
| 16.0.73 | 20 / 9 | |
| 16.0.72 | 20 / 9 | |
| 16.0.71 | 20 / 9 | |
| 16.0.70 | 20 / 9 | |
| 16.0.69 | 20 / 9 | |
| 16.0.68 | 20 / 9 | |
| 16.0.67 | 20 / 9 | |
| 16.0.66 | 20 / 9 | |
| 16.0.65 | 20 / 9 | |
| 16.0.64 | 20 / 9 | |
| 16.0.63 | 20 / 9 | |
| 16.0.62 | 20 / 9 | |
| 16.0.61 | 20 / 9 | |
| 16.0.60 | 20 / 9 | |
| 16.0.59 | 20 / 9 | |
| 16.0.58 | 20 / 9 | |
| 16.0.57 | 20 / 9 | |
| 16.0.56 | 20 / 9 | |
| 16.0.55 | 20 / 9 | |
| 16.0.54 | 20 / 9 | |
| 16.0.53 | 20 / 9 | |
| 16.0.52 | 20 / 9 | |
| 16.0.51 | 20 / 9 | |
| 16.0.50 | 20 / 9 | |
| 16.0.49 | 20 / 9 | |
| 16.0.48 | 20 / 9 | |
| 16.0.47 | 20 / 9 | |
| 16.0.46 | 20 / 9 | |
| 16.0.45 | 20 / 9 | |
| 16.0.44 | 20 / 9 | |
| 16.0.43 | 19 / 9 | |
| 16.0.42 | 19 / 9 | |
| 16.0.41 | 19 / 9 | |
| 16.0.40 | 19 / 9 | |
| 16.0.39 | 19 / 9 | |
| 16.0.38 | 19 / 9 | |
| 16.0.37 | 19 / 9 | |
| 16.0.36 | 19 / 9 | |
| 16.0.35 | 19 / 9 | |
| 16.0.34 | 19 / 9 | |
| 16.0.33 | 19 / 9 | |
| 16.0.32 | 19 / 9 | |
| 16.0.31 | 19 / 9 | |
| 16.0.30 | 19 / 9 | |
| 16.0.29 | 19 / 9 | |
| 16.0.28 | 19 / 9 | |
| 16.0.27 | 19 / 9 | |
| 16.0.26 | 19 / 9 | |
| 16.0.25 | 19 / 9 | |
| 16.0.24 | 19 / 9 | |
| 16.0.23 | 19 / 9 | |
| 16.0.22 | 19 / 9 | |
| 16.0.21 | 19 / 9 | |
| 16.0.20 | 19 / 9 | |
| 16.0.19 | 19 / 9 | |
| 16.0.18 | 19 / 9 | |
| 16.0.17 | 19 / 9 |
v16.0.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.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.
v16.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.
v16.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.
v16.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.
v16.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.
v16.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.
v16.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.
v16.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.
v16.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.
v16.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.
v16.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.
v16.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.