d3-geo — Greenflagged

Shapes and calculators for spherical coordinates.

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-modulegeomapscartography

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Missing gitHead is consistent with a publish environment change during the 2.0.0 major release; no other malicious signals present.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years; absence is expected and not a risk signal for this package.	ai	2026/04/23
npm-metadata	suspicious-initial-version	AI (npm-metadata): Package is 12+ years old with 54 versions; 0.0.0 was a legitimate initial placeholder, not a malicious throwaway version.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): recifs (Philippe Rivière) is the known successor maintainer for D3 modules; this transfer is legitimate and stable.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): mbostock → recifs is a documented, legitimate D3 ecosystem maintainer transition; stable for this package.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): d3-geo is an established D3 module (54 versions, 4407 days old); inflated semver and minimal README are false positives for this context.	ai	2026/04/21
dependencies	unvetted-dep:d3-array	AI (dependencies): d3-array is a sibling D3 module; dependency is legitimate and already accepted in prior versions.	ai	2026/04/21

Versions (showing 52 of 52)

Version	Deps	Published
3.1.1	1 / 10	2024-03-12
3.1.0	1 / 10	2022-12-20
3.0.1	1 / 8	2021-06-05
3.0.0	1 / 8	2021-06-05
2.0.2	1 / 9	2021-06-09
2.0.1	1 / 9	2020-08-26
2.0.0	1 / 9	2020-08-23
1.12.1	1 / 10	2020-05-27
1.12.0	1 / 10	2020-04-18
1.11.9	1 / 10	2019-11-16
1.11.8	1 / 10	2019-11-12
1.11.7	1 / 10	2019-11-07
1.11.6	1 / 8	2019-06-21
1.11.5	1 / 8	2019-06-21
1.11.4	1 / 8	2019-06-21
1.11.3	1 / 8	2018-11-26
1.11.2	1 / 8	2018-11-24
1.11.1	1 / 8	2018-08-24
1.11.0	1 / 8	2018-08-24
1.10.0	1 / 8	2018-03-14
1.9.1	1 / 8	2017-12-08
1.9.0	1 / 8	2017-10-05
1.8.1	1 / 8	2017-09-30
1.7.1	1 / 8	2017-09-13
1.7.0	1 / 8	2017-09-12
1.6.4	1 / 8	2017-05-16
1.6.3	1 / 8	2017-03-13
1.6.2	1 / 8	2017-03-10
1.6.1	1 / 8	2017-03-02
1.6.0	1 / 8	2017-02-28
1.5.0	1 / 8	2017-02-19
1.4.2	1 / 8	2017-02-18
1.4.1	1 / 8	2017-02-09
1.4.0	1 / 8	2016-11-16
1.3.1	1 / 8	2016-10-27
1.3.0	1 / 8	2016-10-27
1.2.6	1 / 8	2016-10-11
1.2.5	1 / 8	2016-09-20
1.2.4	1 / 8	2016-08-20
1.2.3	1 / 8	2016-08-15
1.2.2	1 / 8	2016-08-02
1.2.1	1 / 8	2016-08-02
1.2.0	1 / 8	2016-07-29
1.1.1	1 / 8	2016-07-11
1.1.0	1 / 7	2016-06-30
1.0.0	1 / 7	2016-06-24
0.1.0	1 / 7	2016-06-22
0.0.4	1 / 7	2016-06-20
0.0.3	1 / 7	2016-06-19
0.0.2	1 / 5	2016-06-18
0.0.1	0 / 4	2016-05-02
0.0.0	0 / 3	2014-03-29

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

HIGH Publisher changed: mbostock → recifs (on 2020-08-26) provenance

This version was published by a different npm account than previous versions on 2020-08-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

HIGH Publisher changed: mbostock → recifs (on 2020-08-23) provenance

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.

LOW No provenance attestation provenance

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

v1.12.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

LOW No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2020-05-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-27. This could indicate a legitimate maintainer transition or an account compromise.

v1.12.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

LOW No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2020-04-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-18. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.9

1 finding

LOW No provenance attestation provenance

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

v1.11.8

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

LOW No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2019-11-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-12. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.7

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

LOW No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2019-11-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-07. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.6

1 finding

LOW No provenance attestation provenance

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

v1.11.5

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

LOW No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2019-06-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-21. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.4

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

LOW No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2019-06-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-21. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.3

1 finding

LOW No provenance attestation provenance

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

v1.11.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2018-11-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-24. This could indicate a legitimate maintainer transition or an account compromise.

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

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

v0.0.1

1 finding

LOW No provenance attestation provenance

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

v0.0.0

1 finding

LOW No provenance attestation provenance

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