redux-devtools-test-generator

Generate tests for redux devtools.

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

timdorrzalmoxisusmethuselah96

Keywords

reduxdevtoolstestfluxreacthot 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): methuselah96 is the legitimate new maintainer of redux-devtools packages under the reduxjs org monorepo; transition is consistent with the official repo URL and publisher track record.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Missing gitHead is consistent with migration to a monorepo publish workflow; no malicious signal given the clean package content and legitimate maintainer.	ai	2026/04/24

Versions (showing 20 of 20)

Version	Deps	Published
0.6.2	9 / 35	2020-09-07
0.6.1	9 / 35	2020-08-14
0.6.0	9 / 29	2020-08-02
0.5.1	9 / 41	2017-06-03
0.5.0	8 / 41	2017-03-15
0.4.1	7 / 23	2016-11-24
0.4.0	8 / 23	2016-11-23
0.3.2	8 / 21	2016-11-19
0.3.1	8 / 21	2016-10-10
0.3.0	8 / 21	2016-10-10
0.2.2	8 / 21	2016-08-14
0.2.1	8 / 21	2016-08-14
0.2.0	8 / 21	2016-08-13
0.1.0	5 / 21	2016-08-04
0.0.6	4 / 20	2016-06-27
0.0.5	4 / 20	2016-06-26
0.0.4	4 / 20	2016-06-25
0.0.3	3 / 15	2016-06-22
0.0.2	3 / 15	2016-06-22
0.0.1	2 / 15	2016-06-22

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

2 findings

HIGH Publisher changed: zalmoxisus → methuselah96 (on 2020-08-14) provenance

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

v0.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-08-02) provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.0.1

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.