react-scan
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Well-established package with clean history; single missing gitHead is low risk without other malware signals. | ai | |
| phantom-deps | phantom-dep:react-grab | AI (phantom-deps): react-grab is declared but not directly imported; phantom-dep finding confirms it's not used in code. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:estree-walker | AI (phantom-deps): Referenced in config/build tooling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/generator | AI (phantom-deps): Referenced in config/build tooling; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with public GitHub repo; lack of Sigstore attestation is common and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 13 / 19 | |
| 0.5.7 | 11 / 21 | |
| 0.5.6 | 10 / 20 | |
| 0.5.5 | 10 / 20 | |
| 0.5.4 | 13 / 20 | |
| 0.5.3 | 13 / 19 | |
| 0.5.2 | 13 / 19 | |
| 0.5.1 | 13 / 19 | |
| 0.5.0 | 13 / 19 |
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: abai.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.