d3-time-format
A JavaScript time formatter and parser inspired by strftime and strptime.
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-time-format is a core D3 package published by Mike Bostock (recifs). Missing gitHead is a benign publish-environment change for this trusted publisher. | ai | |
| provenance | publisher-changed | AI (provenance): mbostock is the original D3 author; change from recifs is a legitimate account transition within the D3 org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bumps in mature libraries like D3 modules naturally have long gaps between releases. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2021 before Sigstore provenance was widely adopted; expected for this era. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 1 / 4 | |
| 4.0.0 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.3.0 | 1 / 5 | |
| 2.2.3 | 1 / 5 | |
| 2.2.2 | 1 / 5 | |
| 2.2.1 | 1 / 5 | |
| 2.2.0 | 1 / 5 | |
| 2.1.3 | 1 / 5 | |
| 2.1.2 | 1 / 5 | |
| 2.1.1 | 1 / 6 | |
| 2.1.0 | 1 / 6 | |
| 2.0.5 | 1 / 6 | |
| 2.0.4 | 1 / 6 | |
| 2.0.3 | 1 / 6 | |
| 2.0.2 | 1 / 6 | |
| 2.0.1 | 1 / 6 | |
| 2.0.0 | 1 / 6 | |
| 1.1.0 | 1 / 6 | |
| 1.0.0 | 1 / 5 | |
| 0.4.0 | 1 / 5 | |
| 0.3.2 | 1 / 4 | |
| 0.3.1 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.1 | 1 / 4 | |
| 0.2.0 | 1 / 4 | |
| 0.1.5 | 1 / 4 | |
| 0.1.4 | 1 / 4 | |
| 0.1.3 | 0 / 5 | |
| 0.1.2 | 0 / 5 | |
| 0.1.1 | 0 / 5 | |
| 0.1.0 | 0 / 5 | |
| 0.0.2 | 0 / 5 | |
| 0.0.1 | 0 / 5 | |
| 0.0.0 | 0 / 3 |
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-05. 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.
v3.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.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.