redux-devtools-log-monitor
The default tree view monitor for Redux DevTools
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): timdorr is a well-known Redux core maintainer; addition reflects legitimate org transfer to reduxjs, not a compromise. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is expected after monorepo migration to reduxjs/redux-devtools; publish environment change is legitimate. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from zalmoxisus to methuselah96 reflects the documented migration of Redux DevTools to the reduxjs GitHub org; legitimate maintainer transition, not a compromise. | ai | |
| phantom-deps | phantom-dep:@types/prop-types | AI (phantom-deps): @types/* packages are TypeScript type declarations consumed by the compiler, not imported at runtime. Phantom-dep firing on them is a stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): gaearon is Dan Abramov, original author of Redux/Redux DevTools — a well-known legitimate account. Spam flag is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/lodash.debounce | AI (phantom-deps): @types/* packages are TypeScript type declarations consumed by the compiler, not imported at runtime. Phantom-dep firing on them is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/redux-devtools-themes | AI (phantom-deps): @types/* packages are TypeScript type declarations consumed by the compiler, not imported at runtime. Phantom-dep firing on them is a stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 7 / 4 | |
| 2.0.1 | 5 / 8 | |
| 2.0.0 | 5 / 8 | |
| 1.4.0 | 5 / 15 | |
| 1.3.0 | 5 / 15 | |
| 1.2.0 | 4 / 15 | |
| 1.1.1 | 4 / 15 | |
| 1.1.0 | 4 / 15 | |
| 1.0.11 | 4 / 15 | |
| 1.0.10 | 4 / 15 | |
| 1.0.9 | 3 / 15 | |
| 1.0.8 | 3 / 15 | |
| 1.0.7 | 3 / 15 | |
| 1.0.6 | 3 / 15 | |
| 1.0.5 | 3 / 15 | |
| 1.0.4 | 3 / 15 | |
| 1.0.3 | 3 / 15 | |
| 1.0.2 | 3 / 15 | |
| 1.0.1 | 3 / 15 | |
| 1.0.0 | 3 / 15 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: methuselah96.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-20. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.