redux-devtools — Greenflagged

Redux DevTools with hot reloading and time travel

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

gaearontimdorrzalmoxisusmethuselah96

Keywords

reduxdevtoolsfluxhot reloadingtime travellive edit

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Documented maintainer transition from zalmoxisus to methuselah96 under the reduxjs org in 2020. methuselah96 has 335 approved/0 rejected packages and is a known redux-devtools maintainer.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Missing gitHead is consistent with the publish environment change during the 2020 maintainer/org transition; no malicious signal.	ai	2026/04/24

Versions (showing 33 of 33)

Version	Deps	Published
3.7.0	4 / 6	2020-09-07
3.6.1	3 / 12	2020-08-14
3.6.0	3 / 12	2020-07-28
3.5.0	3 / 22	2018-12-21
3.4.2	3 / 23	2018-11-15
3.4.1	3 / 23	2017-11-11
3.4.0	3 / 23	2017-04-25
3.3.2	2 / 23	2017-01-12
3.3.1	4 / 20	2016-05-09
3.3.0	4 / 21	2016-05-09
3.2.0	3 / 20	2016-04-02
3.1.1	3 / 20	2016-02-08
3.1.0	3 / 20	2016-02-02
3.0.2	3 / 20	2016-01-28
3.0.1	3 / 20	2015-12-27
3.0.0	3 / 17	2015-12-14
2.1.5	4 / 17	2015-09-27
2.1.4	4 / 17	2015-09-25
2.1.3	4 / 17	2015-09-24
2.1.2	4 / 11	2015-09-12
2.1.1	4 / 11	2015-09-12
2.1.0	4 / 11	2015-09-03
2.0.0	4 / 11	2015-09-01
1.1.2	4 / 11	2015-08-26
1.1.1	3 / 11	2015-08-23
1.1.0	3 / 11	2015-08-23
1.0.2	3 / 11	2015-08-12
1.0.0	3 / 11	2015-08-12
0.2.0	2 / 11	2015-08-07
0.1.3	2 / 11	2015-08-05
0.1.2	2 / 11	2015-07-20
0.1.1	2 / 11	2015-07-14
0.1.0	2 / 11	2015-07-14

v3.7.0

1 finding

LOW No provenance attestation provenance

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

v3.6.1

1 finding

LOW No provenance attestation provenance

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

v3.6.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: methuselah96.

HIGH Publisher changed: zalmoxisus → methuselah96 (on 2020-07-28) provenance

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

v3.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

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

v3.4.2

1 finding

LOW No provenance attestation provenance

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

v3.4.1

1 finding

LOW No provenance attestation provenance

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.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: gaearon → zalmoxisus (on 2017-01-12) provenance

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

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

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

1 finding

LOW No provenance attestation provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

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

1 finding

LOW No provenance attestation provenance

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

1 finding

LOW No provenance attestation provenance

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