d3-timer
An efficient queue capable of managing thousands of concurrent animations.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): recifs is a known D3 org maintainer; the mbostock→recifs transition in 2020 is a documented, legitimate handoff consistent across the entire D3 module ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): mbostock is Mike Bostock, the original D3.js author reclaiming publishing rights from a prior delegated publisher. This is a legitimate and well-known transition, not a compromise. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.0.0 | 0 / 4 | |
| 1.0.10 | 0 / 4 | |
| 1.0.9 | 0 / 4 | |
| 1.0.8 | 0 / 4 | |
| 1.0.7 | 0 / 5 | |
| 1.0.6 | 0 / 5 | |
| 1.0.5 | 0 / 5 | |
| 1.0.4 | 0 / 5 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 | |
| 0.5.1 | 0 / 5 | |
| 0.5.0 | 0 / 5 | |
| 0.4.4 | 0 / 4 | |
| 0.4.3 | 0 / 4 | |
| 0.4.2 | 0 / 4 | |
| 0.4.1 | 0 / 4 | |
| 0.4.0 | 0 / 4 | |
| 0.3.2 | 0 / 4 | |
| 0.3.1 | 0 / 4 | |
| 0.3.0 | 0 / 4 | |
| 0.2.0 | 0 / 4 | |
| 0.1.2 | 0 / 4 | |
| 0.1.1 | 0 / 4 | |
| 0.1.0 | 0 / 4 | |
| 0.0.6 | 0 / 4 | |
| 0.0.5 | 0 / 4 | |
| 0.0.4 | 0 / 4 | |
| 0.0.3 | 0 / 4 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 4 |
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.