@elliemae/ds-query-builder
ICE MT - Dimsum - Query Builder
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are direct replacements for removed legacy equivalents within the same @elliemae monorepo at the same version. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-form | AI (dependencies): Sibling monorepo package pinned at matching version; standard Elliemae DS release pattern. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-button | AI (dependencies): Sibling monorepo package pinned at matching version; standard Elliemae DS release pattern. | ai | |
| dependencies | unvetted-dep:@elliemae/ds-popper | AI (dependencies): Sibling monorepo package pinned at matching version; standard Elliemae DS release pattern. | ai | |
| dependencies | unvetted-dep:react-addons-update | AI (dependencies): Legacy React utility; long-standing dependency in this package family, no malware indicators. | ai | |
| provenance | no-provenance | AI (provenance): Large internal ICE MT monorepo; provenance not part of their publish workflow across all versions. | ai |
Versions (showing 100 of 170)
| Version | Deps | Published |
|---|---|---|
| 3.61.8 | 13 / 3 | |
| 3.61.7 | 13 / 3 | |
| 3.61.6 | 13 / 3 | |
| 3.61.5 | 13 / 3 | |
| 3.61.4 | 13 / 3 | |
| 3.61.2 | 13 / 3 | |
| 3.61.1 | 13 / 3 | |
| 3.57.15 | 13 / 4 | |
| 3.57.14 | 13 / 4 | |
| 3.57.13 | 13 / 4 | |
| 3.57.9 | 13 / 4 | |
| 3.57.6 | 13 / 4 | |
| 3.56.3 | 14 / 4 | |
| 3.56.2 | 14 / 4 | |
| 3.55.6 | 14 / 4 | |
| 3.55.2 | 14 / 4 | |
| 3.55.1 | 14 / 4 | |
| 3.54.4 | 14 / 4 | |
| 3.54.2 | 14 / 4 | |
| 3.54.1 | 14 / 4 | |
| 3.54.0 | 14 / 4 | |
| 3.52.1 | 14 / 4 | |
| 3.52.0 | 14 / 4 | |
| 3.51.7 | 14 / 4 | |
| 3.51.6 | 14 / 4 | |
| 3.51.5 | 14 / 4 | |
| 3.51.4 | 14 / 4 | |
| 3.51.3 | 14 / 4 | |
| 3.51.2 | 14 / 4 | |
| 3.51.1 | 14 / 4 | |
| 3.49.8 | 15 / 5 | |
| 3.49.7 | 15 / 5 | |
| 3.49.6 | 15 / 5 | |
| 3.49.5 | 15 / 5 | |
| 3.49.4 | 15 / 5 | |
| 3.49.3 | 15 / 5 | |
| 3.49.2 | 15 / 5 | |
| 3.49.1 | 15 / 5 | |
| 3.49.0 | 15 / 5 | |
| 3.48.1 | 14 / 3 | |
| 3.48.0 | 14 / 3 | |
| 3.47.1 | 14 / 3 | |
| 3.46.7 | 14 / 3 | |
| 3.46.6 | 14 / 3 | |
| 3.46.5 | 14 / 3 | |
| 3.46.4 | 14 / 3 | |
| 3.46.3 | 14 / 3 | |
| 3.46.2 | 14 / 3 | |
| 3.46.1 | 14 / 3 | |
| 3.46.0 | 14 / 3 | |
| 3.45.1 | 14 / 3 | |
| 3.45.0 | 14 / 3 | |
| 3.42.0 | 14 / 3 | |
| 3.41.1 | 14 / 3 | |
| 3.41.0 | 14 / 3 | |
| 3.40.0 | 14 / 3 | |
| 3.39.6 | 14 / 3 | |
| 3.39.5 | 14 / 3 | |
| 3.39.4 | 14 / 3 | |
| 3.39.3 | 14 / 3 | |
| 3.39.2 | 14 / 3 | |
| 3.39.1 | 14 / 3 | |
| 3.39.0 | 14 / 3 | |
| 3.38.0 | 14 / 3 | |
| 3.37.3 | 14 / 3 | |
| 3.37.2 | 14 / 3 | |
| 3.37.1 | 14 / 3 | |
| 3.37.0 | 14 / 3 | |
| 3.35.0 | 15 / 3 | |
| 3.34.0 | 15 / 3 | |
| 3.33.1 | 15 / 3 | |
| 3.33.0 | 15 / 3 | |
| 3.31.8 | 15 / 3 | |
| 3.31.7 | 15 / 3 | |
| 3.31.6 | 15 / 3 | |
| 3.31.5 | 15 / 3 | |
| 3.31.4 | 15 / 3 | |
| 3.31.3 | 15 / 3 | |
| 3.31.1 | 15 / 3 | |
| 3.31.0 | 15 / 3 | |
| 3.30.1 | 15 / 3 | |
| 3.29.1 | 15 / 3 | |
| 3.29.0 | 15 / 3 | |
| 3.27.0 | 15 / 3 | |
| 3.26.0 | 15 / 3 | |
| 3.24.6 | 15 / 3 | |
| 3.24.5 | 15 / 3 | |
| 3.24.4 | 15 / 3 | |
| 3.24.3 | 15 / 3 | |
| 3.24.2 | 15 / 3 | |
| 3.24.1 | 15 / 3 | |
| 3.24.0 | 15 / 3 | |
| 3.23.1 | 15 / 7 | |
| 3.23.0 | 15 / 7 | |
| 3.22.0 | 15 / 7 | |
| 3.21.2 | 15 / 0 | |
| 3.20.4 | 15 / 0 | |
| 3.20.3 | 15 / 0 | |
| 3.20.2 | 15 / 0 | |
| 3.20.1 | 15 / 0 |
v3.61.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.41.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.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.
v3.31.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.
v3.31.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.
v3.31.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.
v3.31.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.
v3.31.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.
v3.31.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.
v3.31.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.
v3.31.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.
v3.30.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.
v3.29.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.
v3.29.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.
v3.27.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.
v3.26.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.
v3.24.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.
v3.24.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.
v3.24.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.
v3.24.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.
v3.24.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.
v3.24.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.
v3.24.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.
v3.23.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.
v3.23.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.
v3.22.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.
v3.21.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.
v3.20.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.
v3.20.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.
v3.20.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.
v3.20.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.