@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, 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 |
|---|---|---|---|---|
| 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 51 of 87)
| Version | Deps | Published |
|---|---|---|
| 4.18.30 | 24 / 9 | |
| 4.18.29 | 24 / 9 | |
| 4.18.28 | 24 / 9 | |
| 4.18.27 | 24 / 9 | |
| 4.18.26 | 24 / 9 | |
| 4.18.25 | 24 / 9 | |
| 4.18.24 | 24 / 9 | |
| 4.18.23 | 24 / 9 | |
| 4.18.22 | 24 / 9 | |
| 4.18.21 | 24 / 9 | |
| 4.18.20 | 24 / 9 | |
| 4.18.19 | 24 / 9 | |
| 4.18.18 | 24 / 9 | |
| 4.18.17 | 24 / 9 | |
| 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 | |
| 4.17.98 | 24 / 9 | |
| 4.17.97 | 24 / 9 | |
| 4.17.96 | 24 / 9 | |
| 4.17.95 | 24 / 9 | |
| 4.17.94 | 24 / 9 | |
| 4.17.93 | 24 / 9 | |
| 4.17.92 | 24 / 9 | |
| 4.17.91 | 24 / 9 | |
| 4.17.90 | 24 / 9 | |
| 4.17.89 | 24 / 9 | |
| 4.17.88 | 24 / 9 | |
| 4.17.87 | 24 / 9 | |
| 4.17.86 | 24 / 9 | |
| 4.17.85 | 24 / 9 | |
| 4.17.84 | 24 / 9 | |
| 4.17.82 | 24 / 9 | |
| 4.17.81 | 24 / 9 | |
| 4.17.80 | 24 / 9 |
v4.18.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.