@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 17 of 117)
| Version | Deps | Published |
|---|---|---|
| 16.0.16 | 19 / 9 | |
| 16.0.15 | 19 / 9 | |
| 16.0.14 | 19 / 9 | |
| 16.0.13 | 19 / 9 | |
| 16.0.12 | 19 / 9 | |
| 16.0.11 | 19 / 9 | |
| 16.0.10 | 19 / 9 | |
| 16.0.9 | 19 / 9 | |
| 16.0.8 | 19 / 9 | |
| 16.0.7 | 19 / 9 | |
| 16.0.6 | 20 / 9 | |
| 16.0.5 | 20 / 9 | |
| 16.0.4 | 20 / 9 | |
| 16.0.3 | 20 / 9 | |
| 16.0.2 | 20 / 9 | |
| 16.0.1 | 21 / 9 | |
| 16.0.0 | 21 / 9 |
v16.0.16
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.15
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.14
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.13
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.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.
v16.0.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.