@finos/legend-application-studio
Legend Studio 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only package loaded by convention in TypeScript projects; not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only package loaded by convention in TypeScript projects; not directly imported. | ai | |
| phantom-deps | phantom-dep:@testing-library/dom | AI (phantom-deps): Testing utility pulled in transitively by @testing-library/react; phantom detection is a false positive here. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 28.21.12 | 35 / 9 | |
| 28.21.11 | 35 / 9 | |
| 28.21.10 | 35 / 9 | |
| 28.21.9 | 35 / 9 | |
| 28.21.8 | 35 / 9 | |
| 28.21.7 | 35 / 9 | |
| 28.21.6 | 35 / 9 | |
| 28.21.5 | 35 / 9 | |
| 28.21.4 | 35 / 9 | |
| 28.21.3 | 35 / 9 | |
| 28.21.2 | 35 / 9 | |
| 28.21.1 | 35 / 9 | |
| 28.21.0 | 35 / 9 | |
| 28.20.0 | 32 / 9 | |
| 28.19.117 | 32 / 9 | |
| 28.19.116 | 32 / 9 | |
| 28.19.115 | 32 / 9 | |
| 28.19.114 | 32 / 9 | |
| 28.19.113 | 32 / 9 | |
| 28.19.112 | 32 / 9 |
v28.21.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.19.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.19.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.19.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.19.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v28.19.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.