react-datetime — Greenflagged

A lightweight but complete datetime picker React.js component

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

arqexsimeglayneanderson

Keywords

reactreact-componentdatepickertimepickerdatetimepickerdatetime

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): react-datetime is a long-established package (3961 days, 83 versions) with a clean track record. Lack of Sigstore provenance is a process gap, not a security indicator for this package.	ai	2026/04/24
phantom-deps	phantom-dep:react-onclickoutside	AI (phantom-deps): react-onclickoutside is a declared runtime dependency in package.json; the phantom-dep finding reflects a config-file reference pattern, not a true undeclared dependency.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change (arqex→simeg) occurred in Dec 2016, 8+ years ago. Repo URL still points to original author; simeg has 60 approved packages and 0 rejected. Legitimate historical transition.	ai	2026/04/24

Versions (showing 70 of 70)

Version	Deps	Published
3.3.1	1 / 71	2024-12-13
3.3.0	1 / 71	2024-12-12
3.2.0	1 / 71	2022-10-27
3.1.1	1 / 71	2021-09-06
3.1.0	1 / 71	2021-09-02
3.0.4	1 / 72	2020-09-23
3.0.3	1 / 72	2020-09-21
3.0.2	1 / 72	2020-09-20
3.0.1	1 / 72	2020-09-19
2.16.3	4 / 33	2018-12-03
2.16.2	4 / 33	2018-10-22
2.16.0	4 / 33	2018-10-18
2.15.0	4 / 32	2018-07-24
2.14.0	4 / 32	2018-02-11
2.13.0	4 / 32	2018-02-09
2.12.0	4 / 32	2018-01-27
2.11.1	4 / 32	2017-12-01
2.11.0	4 / 32	2017-11-13
2.10.3	4 / 31	2017-09-29
2.10.2	4 / 31	2017-09-23
2.10.1	5 / 30	2017-08-27
2.10.0	5 / 30	2017-08-26
2.9.0	4 / 30	2017-07-30
2.8.11	4 / 30	2017-07-27
2.8.10	4 / 31	2017-04-24
2.8.9	2 / 31	2017-04-08
2.8.8	2 / 31	2017-03-01
2.8.7	2 / 31	2017-02-27
2.8.6	2 / 31	2017-02-10
2.8.5	2 / 31	2017-02-09
2.8.4	2 / 17	2017-02-05
2.8.3	2 / 17	2017-01-10
2.8.2	2 / 17	2017-01-06
2.8.1	2 / 17	2016-12-21
2.8.0	2 / 17	2016-12-20
2.7.5	2 / 15	2016-11-18
2.7.4	2 / 15	2016-11-18
2.7.3	2 / 15	2016-11-17
2.7.2	2 / 15	2016-11-17
2.7.1	2 / 15	2016-11-16
2.7.0	2 / 15	2016-11-16
2.6.2	2 / 16	2016-10-27
2.6.1	2 / 16	2016-10-27
2.6.0	2 / 15	2016-09-06
2.5.0	2 / 14	2016-07-29
2.4.0	2 / 12	2016-07-19
2.3.3	2 / 11	2016-07-14
2.3.2	2 / 11	2016-06-17
2.3.1	2 / 11	2016-06-13
2.3.0	2 / 11	2016-06-13
2.2.1	2 / 11	2016-05-24
2.2.0	2 / 11	2016-05-23
2.1.0	2 / 10	2016-02-29
2.0.3	2 / 10	2016-01-28
2.0.2	2 / 10	2015-12-28
2.0.1	2 / 10	2015-11-20
2.0.0	2 / 10	2015-11-09
1.3.0	2 / 10	2015-10-14
1.2.1	2 / 10	2015-08-24
1.2.0	2 / 10	2015-08-24
1.1.1	3 / 10	2015-08-22
1.1.0	3 / 10	2015-08-20
1.0.0	3 / 10	2015-07-30
0.5.0	3 / 8	2015-07-14
0.4.3	2 / 8	2015-07-09
0.4.2	2 / 8	2015-07-09
0.4.1	2 / 8	2015-07-09
0.4.0	2 / 8	2015-07-06
0.3.1	2 / 8	2015-06-22
0.1.0	2 / 11	2015-06-20

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

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.

v2.16.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.

v2.16.2

2 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: arqex.

LOW No provenance attestation provenance

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

v2.16.0

2 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: arqex.

LOW No provenance attestation provenance

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

v2.15.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: arqex.

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: simeg → arqex (on 2018-07-24) provenance

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

v2.14.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.

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.12.0

1 finding

LOW No provenance attestation provenance

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

v2.11.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.

v2.11.0

2 findings

HIGH Publisher changed: layneanderson → simeg (on 2017-11-13) provenance

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

2 findings

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: simeg → layneanderson (on 2017-09-29) provenance

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

v2.10.2

2 findings

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: layneanderson → simeg (on 2017-09-23) provenance

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

v2.10.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.

v2.10.0

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: simeg → layneanderson (on 2017-08-26) provenance

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

v2.9.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.

v2.8.11

1 finding

LOW No provenance attestation provenance

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

v2.8.10

1 finding

LOW No provenance attestation provenance

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

v2.8.9

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: arqex → simeg (on 2017-04-08) provenance

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

v2.8.8

1 finding

LOW No provenance attestation provenance

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

v2.8.7

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: simeg → arqex (on 2017-02-27) provenance

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

v2.8.6

1 finding

LOW No provenance attestation provenance

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

v2.8.5

1 finding

LOW No provenance attestation provenance

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

v2.8.4

1 finding

LOW No provenance attestation provenance

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

v2.8.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.

v2.8.2

1 finding

LOW No provenance attestation provenance

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

v2.8.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.

v2.8.0

2 findings

HIGH Publisher changed: arqex → simeg (on 2016-12-20) provenance

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

2 findings

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: simeg → arqex (on 2016-11-18) provenance

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

v2.7.4

1 finding

LOW No provenance attestation provenance

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

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

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

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

v2.7.0

2 findings

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: arqex → simeg (on 2016-11-16) provenance

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

v2.6.2

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

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

v2.5.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.

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.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.

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

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

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

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

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

v2.1.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.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.

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

v2.0.1

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.

v2.0.0

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.