@gatsbyjs/webpack-hot-middleware
Webpack hot reloading you can attach to your own server
2
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
j0sh77mcolelittletyhoppkgarbayamarvinjudehkpvorozhepauliescanlonkylemathewsleithonenglishdschaupiehwardpeettylerbarnesfksmthomaslekoartsdmccrawabhiaiyerjulienprachelbahldaniellewgatsbyverysprymlgualtieri-gatsbygatsby_integrations
Keywords
webpackhmrhotmodulereloadinghot-reloadingmiddlewareexpress
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Gatsby org team rotation; wardpeet is a long-standing trusted publisher. Large team additions are expected for an active OSS org, not indicative of takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removals are part of the same Gatsby org team rotation. No evidence of hostile takeover; publisher track record is clean. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ansi-html-community is a security-patched fork of ansi-html (fixes ReDoS). This is a deliberate, beneficial dependency swap, not a supply-chain injection. | ai |
v2.25.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.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.