← Home

webpack-serve-overlay

npm Repository Homepage

Error overlay for webpack-serve

4
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

g-rath

Keywords

webpackwebpack-serve

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process usage is confined to a developer release/versioning script (scripts/functions/addFilesToGit.js), not in any runtime code consumed by package users. Stable false positive for this package. ai
provenance no-provenance AI (provenance): Package is 2855 days old, predating Sigstore provenance on npm. Absence is expected and not a risk signal here. ai

Versions (showing 4 of 4)

Version Deps Published
0.3.0 2 / 0
0.2.2 2 / 0
0.2.0 2 / 0
0.1.0 2 / 0

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
INFO No provenance attestation provenance

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

v0.2.0

1 finding
INFO No provenance attestation provenance

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

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