← Home

babel-preset-react-hmre

npm Repository Homepage

Babel preset for React HMR and Error Catching

6
Versions
ISC
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

danmartinez101gaearon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is 10+ years old with 19k weekly downloads; 0.0.0 versioning reflects early ecosystem conventions, not malicious intent. ai
phantom-deps phantom-dep:react AI (phantom-deps): Babel preset references transforms by name string in config, not via require(). Phantom dep detection is a false positive for this pattern. ai
phantom-deps phantom-dep:redbox-react AI (phantom-deps): Same as above — referenced in Babel preset config by name, not imported directly. ai
phantom-deps phantom-dep:react-transform-hmr AI (phantom-deps): Same as above — referenced in Babel preset config by name, not imported directly. ai
phantom-deps phantom-dep:react-transform-catch-errors AI (phantom-deps): Same as above — referenced in Babel preset config by name, not imported directly. ai

Versions (showing 6 of 6)

Version Deps Published
1.1.1 4 / 3
1.1.0 4 / 3
1.0.1 4 / 3
1.0.0 4 / 0
0.0.1 5 / 0
0.0.0 5 / 0

v1.1.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: danmartinez101 → gaearon (on 2016-03-06, known maintainer) provenance

This version was published by a different npm account (gaearon) than the most recent previously approved version (danmartinez101) on 2016-03-06, but gaearon is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.

v0.0.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.