react-devtools-core
Use react-devtools outside of the browser
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/648.chunk.js | AI (source-diff): Webpack chunk output for React DevTools hook-name parsing; minified build artifact with source map included. | ai | |
| source-diff | net-exec-file:dist/648.chunk.js | AI (source-diff): fetch() calls load source files/maps for hook name resolution — core DevTools functionality, not malware. | ai | |
| bogus-package | bogus-package | AI (bogus-package): gaearon (Dan Abramov) is a known React team member; spam flag is erroneous. No keywords is normal for facebook/react packages. | ai |
Versions (showing 51 of 146)
| Version | Deps | Published |
|---|---|---|
| 7.0.1 | 2 / 5 | |
| 7.0.0 | 2 / 5 | |
| 6.1.5 | 2 / 5 | |
| 6.1.4 | 2 / 5 | |
| 6.1.3 | 2 / 5 | |
| 6.1.2 | 2 / 5 | |
| 6.1.1 | 2 / 5 | |
| 6.1.0 | 2 / 5 | |
| 6.0.1 | 2 / 5 | |
| 6.0.0 | 2 / 5 | |
| 5.3.2 | 2 / 5 | |
| 5.3.1 | 2 / 5 | |
| 5.3.0 | 2 / 5 | |
| 5.2.0 | 2 / 5 | |
| 5.1.0 | 2 / 5 | |
| 5.0.2 | 2 / 5 | |
| 5.0.0 | 2 / 5 | |
| 4.28.5 | 2 / 5 | |
| 4.28.4 | 2 / 5 | |
| 4.28.0 | 2 / 5 | |
| 4.27.8 | 2 / 1 | |
| 4.27.7 | 2 / 1 | |
| 4.27.6 | 2 / 1 | |
| 4.27.5 | 2 / 1 | |
| 4.27.4 | 2 / 1 | |
| 4.27.3 | 2 / 1 | |
| 4.27.2 | 2 / 1 | |
| 4.27.1 | 2 / 1 | |
| 4.27.0 | 2 / 1 | |
| 4.26.1 | 2 / 1 | |
| 4.26.0 | 2 / 1 | |
| 4.25.0 | 2 / 1 | |
| 4.24.7 | 2 / 1 | |
| 4.24.6 | 2 / 1 | |
| 4.24.5 | 2 / 1 | |
| 4.24.4 | 2 / 1 | |
| 4.24.3 | 2 / 1 | |
| 4.24.2 | 2 / 1 | |
| 4.24.1 | 2 / 1 | |
| 4.24.0 | 2 / 1 | |
| 4.23.0 | 2 / 1 | |
| 4.22.1 | 2 / 1 | |
| 4.22.0 | 2 / 1 | |
| 4.21.0 | 2 / 1 | |
| 4.20.2 | 2 / 1 | |
| 4.20.1 | 2 / 1 | |
| 4.20.0 | 2 / 1 | |
| 4.19.2 | 2 / 1 | |
| 4.19.1 | 2 / 1 | |
| 4.19.0 | 2 / 1 | |
| 4.18.0 | 2 / 1 |
v7.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.