d3-dispatch
Register named callbacks and call them with arguments.
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-dispatch is a core D3 module; missing gitHead is due to legitimate publish environment change during D3 org transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): recifs (Philippe Rivière) is a known D3 collaborator; this is a legitimate maintainer transition for the D3 project. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to mbostock, the original author of d3. Legitimate transition from alternate/collaborator account. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2021 before Sigstore provenance was standard practice; d3 core module by known author. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.0.0 | 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.5.0 | 0 / 5 | |
| 0.4.4 | 0 / 5 | |
| 0.4.3 | 0 / 4 | |
| 0.4.2 | 0 / 4 | |
| 0.4.1 | 0 / 4 | |
| 0.4.0 | 0 / 4 | |
| 0.3.0 | 0 / 4 | |
| 0.2.6 | 0 / 4 | |
| 0.2.5 | 0 / 4 | |
| 0.2.4 | 0 / 4 | |
| 0.2.3 | 0 / 4 | |
| 0.2.2 | 0 / 4 | |
| 0.2.1 | 0 / 4 | |
| 0.2.0 | 0 / 4 | |
| 0.1.0 | 0 / 4 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 4 | |
| 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.
[Accepted risk] 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.