← Home

webpack-serve

A CLI for webpack-plugin-serve, providing a premier webpack development server

25
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

shellscape

Keywords

developmentdevserverserveserverwebpack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in lib/config.js is a config-file loader pattern — intentionally loads user-specified webpack config files. This is expected behavior for a webpack CLI tool. ai
publish-pattern dormant-publish AI (publish-pattern): shellscape is a long-established publisher with 1500 approved packages. The gap reflects a major version bump, not an account takeover signal. ai

Versions (showing 25 of 25)

Version Deps Published
4.0.0 10 / 17
3.2.0 10 / 17
3.1.1 10 / 18
3.1.0 10 / 18
3.0.0 10 / 17
2.0.3 31 / 26
2.0.2 31 / 27
2.0.1 31 / 27
2.0.0 31 / 27
1.0.4 24 / 20
1.0.3 24 / 20
1.0.2 24 / 20
1.0.1 24 / 20
1.0.0 24 / 20
0.3.2 23 / 18
0.3.1 23 / 18
0.3.0 21 / 18
0.2.0 21 / 17
0.1.5 20 / 16
0.1.4 19 / 16
0.1.3 19 / 16
0.1.2 19 / 16
0.1.1 19 / 16
0.1.0 19 / 16
0.0.0 0 / 0

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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