react-scanner
1
Versions
—
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
imjakechapmanmoroshko
Keywords
reactscannercomponentcomponentsjsxusageinfostatsstatistics
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): CLI config-loader pattern; require(configPath) is user-supplied and intentional for this tool. | ai | |
| phantom-deps | phantom-dep:picomatch | AI (phantom-deps): picomatch is a declared runtime dep used indirectly via fdir/config; stable false positive. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a declared runtime dep used as a parser library; stable false positive. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 9 / 9 |
v1.2.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.