@finos/legend-shared
Legend Studio shared utilities and helpers
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/pako | AI (phantom-deps): @types packages declared for TypeScript consumers; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): @types packages declared for TypeScript consumers; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@types/lodash-es | AI (phantom-deps): @types packages declared for TypeScript consumers; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@types/papaparse | AI (phantom-deps): @types packages declared for TypeScript consumers; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@types/seedrandom | AI (phantom-deps): @types packages declared for TypeScript consumers; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@types/object-hash | AI (phantom-deps): @types packages declared for TypeScript consumers; not directly imported by convention. | ai | |
| phantom-deps | phantom-dep:@testing-library/dom | AI (phantom-deps): Testing utility declared as runtime dep for downstream test consumers; phantom detection is a false positive here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 11.0.25 | 25 / 9 | |
| 11.0.24 | 25 / 9 | |
| 11.0.23 | 25 / 9 | |
| 11.0.22 | 24 / 9 | |
| 11.0.21 | 24 / 9 | |
| 11.0.20 | 24 / 9 | |
| 11.0.19 | 24 / 9 | |
| 11.0.18 | 24 / 9 | |
| 11.0.17 | 24 / 9 | |
| 11.0.16 | 24 / 9 | |
| 11.0.15 | 24 / 9 | |
| 11.0.14 | 24 / 9 | |
| 11.0.13 | 24 / 9 | |
| 11.0.12 | 24 / 9 |
v11.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.