← Home

redux-devtools-trace-monitor

npm Repository Homepage

Submonitor for Redux DevTools inspector to show stack traces.

6
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

timdorrzalmoxisusmethuselah96

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:lib/openFile.js AI (source-diff): openFile.js uses Chrome DevTools Extension APIs (chrome.devtools.panels.openResource, chrome.tabs.create) to open source files in DevTools — standard browser extension behavior, not malware. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): chalk is a legitimate utility dependency; phantom detection is a packaging/bundling artifact, not a security issue for this package. ai
provenance publisher-changed AI (provenance): Documented transition: redux-devtools monorepo moved to reduxjs org; methuselah96 (Mark Erikson) is a core Redux maintainer. Original author zalmoxisus remains listed as contributor. ai
bogus-package bogus-package AI (bogus-package): README link dump is typical for monorepo sub-packages linking to parent repo and related packages. Not indicative of spam or phishing for this established ecosystem package. ai

Versions (showing 6 of 6)

Version Deps Published
0.1.3 6 / 15
0.1.2 6 / 15
0.1.1 7 / 16
0.1.0 7 / 27
0.0.3 6 / 27
0.0.2 6 / 27

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

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

2 findings
HIGH New file with network + code execution: lib/openFile.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.1.0

2 findings
HIGH New file with network + code execution: lib/openFile.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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