d3-ease
Easing functions for smooth animation.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): d3-ease is a core d3 module; missing gitHead reflects npm CLI/environment change during v2 publish, not a security concern. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from recifs to mbostock is a known account consolidation by Mike Bostock, the D3 author. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.0.0 | 0 / 4 | |
| 1.0.7 | 0 / 4 | |
| 1.0.6 | 0 / 4 | |
| 1.0.5 | 0 / 4 | |
| 1.0.4 | 0 / 4 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 | |
| 0.8.0 | 0 / 5 | |
| 0.7.0 | 0 / 4 | |
| 0.6.0 | 0 / 4 | |
| 0.5.2 | 0 / 4 | |
| 0.5.1 | 0 / 4 | |
| 0.5.0 | 0 / 4 | |
| 0.4.0 | 0 / 4 | |
| 0.3.1 | 0 / 4 | |
| 0.3.0 | 0 / 4 | |
| 0.2.1 | 0 / 4 | |
| 0.2.0 | 0 / 4 | |
| 0.1.5 | 0 / 4 | |
| 0.1.4 | 0 / 4 | |
| 0.1.3 | 0 / 4 | |
| 0.1.2 | 0 / 4 | |
| 0.1.1 | 0 / 4 | |
| 0.1.0 | 0 / 4 | |
| 0.0.2 | 0 / 3 | |
| 0.0.1 | 0 / 3 | |
| 0.0.0 | 0 / 3 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-23. This could indicate a legitimate maintainer transition or an account compromise.