← Home

d3-time

A calculator for humanity’s peculiar conventions of time.

37
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-moduletimeintervalcalendar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): d3-time is a core D3 module; missing gitHead is a minor provenance gap from the 2020 publish environment, not a security concern. ai
maintainer-change maintainer-added AI (maintainer-change): recifs (Philippe Rivière) is a known D3 collaborator; this is a legitimate maintainer transition within the D3 org. ai
provenance publisher-changed AI (provenance): Publisher change from recifs to mbostock is the original D3 author consolidating publishing; stable for this package. ai
provenance no-provenance AI (provenance): Pre-Sigstore era package from a highly trusted publisher; no provenance expected for older d3 modules. ai
publish-pattern new-deps-added AI (publish-pattern): d3-array is a sibling D3 module by the same author; intra-ecosystem dependency is expected. ai

Versions (showing 37 of 37)

Version Deps Published
3.1.0 1 / 4
3.0.0 1 / 4
2.1.1 1 / 4
2.1.0 1 / 4
2.0.0 0 / 4
1.1.0 0 / 4
1.0.11 0 / 4
1.0.10 0 / 4
1.0.9 0 / 4
1.0.8 0 / 5
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.3.2 0 / 5
0.3.1 0 / 5
0.3.0 0 / 5
0.2.6 0 / 5
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.1 0 / 4
0.1.0 0 / 4
0.0.7 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.0 0 / 3

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.1.1

2 findings
HIGH Publisher changed: recifs → mbostock (on 2021-04-10) provenance

This version was published by a different npm account than previous versions on 2021-04-10. 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.1.0

2 findings
HIGH Publisher changed: recifs → mbostock (on 2021-04-10) provenance

This version was published by a different npm account than previous versions on 2021-04-10. 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.

INFO No provenance attestation provenance

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

INFO Publisher changed: mbostock → recifs (on 2020-08-13) provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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