redux-devtools-chart-monitor MIT 22 versions

redux-devtools-chart-monitor

npm Repository Homepage

Chart monitor for Redux DevTools

22

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

timdorrromseguyzalmoxisuskachkaevmethuselah96

Keywords

reduxdevtoolsfluxreactchart

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition to reduxjs org maintainer (methuselah96); repo points to official reduxjs/redux-devtools monorepo. Publisher has strong track record with 346 approved packages.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): kachkaev added as part of the Redux DevTools monorepo consolidation under the reduxjs org; consistent with the documented 2020 transition.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): prop-types is the official React prop-types library (Facebook/Meta), one of the most trusted npm packages. Adding it to a React component library is entirely expected.	ai	2026/04/24

Versions (showing 22 of 22)

Version	Deps	Published
1.7.2	5 / 8	2020-09-07
1.7.1	5 / 8	2020-08-14
1.7.0	5 / 12	2018-01-09
1.6.1	4 / 12	2016-11-25
1.6.0	4 / 12	2016-11-21
1.5.1	4 / 12	2016-10-14
1.5.0	4 / 12	2016-10-14
1.4.2	4 / 12	2016-08-01
1.4.1	4 / 12	2016-04-16
1.4.0	4 / 12	2016-04-10
1.3.0	4 / 12	2016-04-10
1.2.2	4 / 12	2016-04-06
1.2.1	4 / 12	2016-03-30
1.2.0	4 / 12	2016-02-28
1.1.3	4 / 12	2016-01-12
1.1.2	4 / 12	2016-01-11
1.1.1	4 / 12	2016-01-11
1.1.0	4 / 12	2016-01-11
1.0.2	4 / 12	2016-01-10
1.0.1	4 / 12	2016-01-08
1.0.0	5 / 12	2015-12-14
0.1.0	4 / 9	2015-09-27

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

2 findings

HIGH Publisher changed: romseguy → 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.

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.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. Only ~12% of npm packages have provenance, so this is common but not ideal.