@elliemae/ds-tooltip
ICE MT - Dimsum - Tooltip
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@elliemae/ds-button | AI (phantom-deps): Same-org monorepo sibling; declared but may be re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-popperjs | AI (phantom-deps): Same-org monorepo sibling; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Large ICE MT monorepo; no provenance is consistent across all versions of this package family. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this tooltip package. | ai | |
| phantom-deps | phantom-dep:@elliemae/ds-legacy-button-v1 | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.61.5 | 10 / 6 | |
| 3.61.4 | 10 / 6 | |
| 3.61.2 | 10 / 6 | |
| 3.61.1 | 10 / 6 | |
| 3.57.15 | 11 / 9 | |
| 3.57.14 | 11 / 9 | |
| 3.57.13 | 11 / 9 | |
| 3.56.3 | 11 / 9 | |
| 3.56.2 | 11 / 9 | |
| 3.55.2 | 11 / 9 | |
| 3.55.1 | 11 / 9 | |
| 3.54.4 | 11 / 9 | |
| 3.54.2 | 11 / 9 | |
| 3.54.1 | 11 / 9 | |
| 3.54.0 | 11 / 9 | |
| 3.52.1 | 11 / 8 | |
| 3.52.0 | 11 / 8 |
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.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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.