dateformat — Greenflagged

A node.js package for Steven Levithan's excellent dateFormat() function.

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

felixgectavanjonschlinkertdoowbfpintoschase-manning

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition to chase-manning in 2020; publisher has strong track record (33 approved, 0 rejected, 5+ years active).	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): chase-manning is a known, trusted publisher added as part of a legitimate maintainer transition.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2020 before Sigstore provenance was available; expected for this era of packages.	ai	2026/04/24

Versions (showing 32 of 32)

Show 1 prerelease

Version	Deps	Published
5.0.3	0 / 5	2022-02-19
5.0.2	0 / 5	2021-10-16
5.0.1	0 / 5	2021-09-21
5.0.0	0 / 5	2021-09-21
4.6.3	0 / 5	2021-09-21
4.6.2	0 / 5	2021-09-21
4.6.1	0 / 5	2021-09-21
4.6.0	0 / 5	2021-09-21
4.5.1	0 / 5	2021-01-30
4.5.0	0 / 5	2021-01-23
4.4.2	0 / 5	2021-01-21
4.4.1	0 / 5	2020-12-22
4.4.0	0 / 5	2020-12-22
4.3.1	0 / 5	2020-12-05
4.2.2	0 / 5	2020-12-04
4.2.1	0 / 5	2020-12-04
4.2.0	0 / 4	2020-12-04
4.1.0	0 / 4	2020-12-04
4.0.2	0 / 4	2020-12-04
4.0.1	0 / 4	2020-12-04
4.0.0	0 / 5	2020-11-19
3.0.3	0 / 2	2018-02-09
3.0.2	0 / 2	2017-09-21
3.0.1	0 / 2	2017-09-21
3.0.0	0 / 2	2017-09-19
2.2.0	0 / 2	2017-09-21
2.0.0	0 / 2	2016-11-25
1.0.12	2 / 2	2015-11-19
1.0.11	2 / 2	2014-11-28
1.0.10	2 / 3	2014-11-28
1.0.9	2 / 3	2014-11-27
1.0.8	0 / 0	2014-09-16

v5.0.2

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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

v4.6.3

1 finding

LOW No provenance attestation provenance

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

v4.6.2

1 finding

LOW No provenance attestation provenance

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

v4.6.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.

v4.6.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.

v4.5.1

1 finding

LOW No provenance attestation provenance

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

v4.5.0

1 finding

LOW No provenance attestation provenance

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

v4.4.2

1 finding

LOW No provenance attestation provenance

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

v4.4.1

1 finding

LOW No provenance attestation provenance

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

v4.4.0

1 finding

LOW No provenance attestation provenance

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

v4.3.1

1 finding

LOW No provenance attestation provenance

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

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

2 findings

HIGH Publisher changed: doowb → chase-manning (on 2020-12-04) provenance

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

v4.0.0

2 findings

HIGH Publisher changed: doowb → chase-manning (on 2020-11-19) provenance

This version was published by a different npm account than previous versions on 2020-11-19. 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.