@finos/legend-query-builder
Legend query builder 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:serializr | AI (dependencies): serializr is a well-known, stable serialization library; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/runtime dep declared for consumers; not directly imported in source is expected for a library. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped type package; loaded by convention in TypeScript React projects. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Framework-scoped type package; loaded by convention in TypeScript React projects. | ai | |
| phantom-deps | phantom-dep:@testing-library/dom | AI (phantom-deps): Testing utility loaded transitively by @testing-library/react; not directly imported is expected. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.18.16 | 24 / 9 | |
| 4.18.15 | 24 / 9 | |
| 4.18.14 | 24 / 9 | |
| 4.18.13 | 24 / 9 | |
| 4.18.12 | 24 / 9 | |
| 4.18.11 | 24 / 9 | |
| 4.18.10 | 24 / 9 | |
| 4.18.9 | 24 / 9 | |
| 4.18.8 | 24 / 9 | |
| 4.18.7 | 24 / 9 | |
| 4.18.6 | 24 / 9 | |
| 4.18.5 | 24 / 9 | |
| 4.18.4 | 24 / 9 | |
| 4.18.3 | 24 / 9 | |
| 4.18.2 | 24 / 9 | |
| 4.18.1 | 24 / 9 | |
| 4.18.0 | 24 / 9 | |
| 4.17.100 | 24 / 9 | |
| 4.17.99 | 24 / 9 |
v4.18.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.