d3-brush
Select a one- or two-dimensional region using the mouse or touch.
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 ecosystem package published by long-standing maintainer; missing gitHead is a metadata artifact, not a security concern. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from recifs to mbostock (D3 creator). This is a legitimate maintainer transition for the D3 ecosystem's major version bump. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 287-day gap is expected for a major version bump (v2→v3) of a mature D3 module. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2021 before npm provenance support existed; stable for this package's older versions. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 5 / 4 | |
| 2.1.0 | 5 / 4 | |
| 2.0.1 | 5 / 4 | |
| 2.0.0 | 5 / 4 | |
| 1.1.6 | 5 / 4 | |
| 1.1.5 | 5 / 4 | |
| 1.1.4 | 5 / 4 | |
| 1.1.3 | 5 / 4 | |
| 1.1.2 | 5 / 4 | |
| 1.1.1 | 5 / 4 | |
| 1.1.0 | 5 / 4 | |
| 1.0.6 | 5 / 4 | |
| 1.0.5 | 5 / 4 | |
| 1.0.4 | 5 / 5 | |
| 1.0.3 | 5 / 5 | |
| 1.0.2 | 5 / 5 | |
| 1.0.1 | 5 / 5 | |
| 1.0.0 | 5 / 5 | |
| 0.2.3 | 5 / 5 | |
| 0.2.2 | 5 / 5 | |
| 0.2.1 | 5 / 5 | |
| 0.2.0 | 5 / 5 | |
| 0.1.6 | 5 / 5 | |
| 0.1.5 | 5 / 5 | |
| 0.1.4 | 5 / 5 | |
| 0.1.3 | 5 / 5 | |
| 0.1.2 | 5 / 5 | |
| 0.1.1 | 5 / 5 | |
| 0.1.0 | 5 / 5 | |
| 0.0.4 | 1 / 0 | |
| 0.0.3 | 1 / 0 | |
| 0.0.2 | 1 / 0 | |
| 0.0.1 | 0 / 0 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-10. 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.1.0
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: recifs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
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: recifs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
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: recifs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.