@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 — the axios compromise (March 2026) relied on exactly this gap.
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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 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 |
v3.61.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.57.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: encw.dev.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.9
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.57.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.56.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.56.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.55.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.55.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.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.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.52.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.52.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.