d3-transition ISC 42 versions

d3-transition

npm Repository Homepage

Animated transitions for D3 selections.

42

Versions

ISC

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mbostockrecifs

Keywords

d3d3-moduledomtransitionanimation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:d3-ease	AI (dependencies): d3-ease is a core D3 sub-module by the same author (mbostock); unvetted status is a pipeline artifact, not a real risk.	ai	2026/04/21
dependencies	unvetted-dep:d3-color	AI (dependencies): d3-color is a core D3 sub-module by the same author (mbostock); unvetted status is a pipeline artifact, not a real risk.	ai	2026/04/21
dependencies	unvetted-dep:d3-timer	AI (dependencies): d3-timer is a core D3 sub-module by the same author (mbostock); unvetted status is a pipeline artifact, not a real risk.	ai	2026/04/21
dependencies	unvetted-dep:d3-dispatch	AI (dependencies): d3-dispatch is a core D3 sub-module by the same author (mbostock); unvetted status is a pipeline artifact, not a real risk.	ai	2026/04/21
dependencies	unvetted-dep:d3-interpolate	AI (dependencies): d3-interpolate is a core D3 sub-module by the same author (mbostock); unvetted status is a pipeline artifact, not a real risk.	ai	2026/04/21
provenance	no-provenance	AI (provenance): Established D3 module predating Sigstore provenance; no provenance is expected and not a risk signal for this package.	ai	2026/04/21

Versions (showing 42 of 42)

Version	Deps	Published
3.0.1	5 / 6	2021-06-09
3.0.0	5 / 6	2021-06-07
2.0.0	5 / 6	2020-08-23
1.3.2	6 / 5	2019-11-18
1.3.1	6 / 5	2019-11-17
1.3.0	6 / 5	2019-11-17
1.2.1	6 / 5	2019-11-16
1.2.0	6 / 5	2019-01-25
1.1.3	6 / 5	2018-08-24
1.1.2	6 / 5	2018-08-24
1.1.1	6 / 6	2017-11-21
1.1.0	6 / 6	2017-05-15
1.0.4	6 / 6	2017-03-10
1.0.3	6 / 6	2016-10-20
1.0.2	6 / 6	2016-08-26
1.0.1	6 / 6	2016-08-02
1.0.0	6 / 6	2016-06-24
0.3.1	6 / 6	2016-06-19
0.3.0	6 / 6	2016-06-08
0.2.10	6 / 6	2016-05-20
0.2.9	6 / 6	2016-05-16
0.2.8	6 / 5	2016-03-06
0.2.7	6 / 5	2016-03-03
0.2.6	6 / 5	2016-03-02
0.2.5	5 / 5	2016-02-28
0.2.4	5 / 5	2016-02-26
0.2.3	5 / 5	2016-02-26
0.2.2	5 / 5	2016-02-24
0.2.1	5 / 5	2016-02-23
0.2.0	5 / 5	2016-02-22
0.1.3	5 / 5	2016-02-22
0.1.2	5 / 5	2016-02-12
0.1.1	5 / 5	2016-02-12
0.1.0	5 / 5	2016-02-11
0.0.9	5 / 5	2016-02-10
0.0.8	5 / 5	2016-02-05
0.0.7	4 / 5	2016-02-03
0.0.6	3 / 5	2015-11-11
0.0.5	3 / 5	2015-11-04
0.0.4	0 / 8	2015-06-16
0.0.3	0 / 6	2015-06-02
0.0.2	0 / 6	2015-05-29

v1.3.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.10

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.9

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.8

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.7

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.9

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.8

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.