webpack-dev-middleware
A development middleware for webpack
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package transitioned to GitHub Actions CI/CD publishing with SLSA provenance attestation under the official webpack org. This is a legitimate and improved release practice, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are consistent with the webpack organization's contributor base. Package has SLSA provenance and is published from the official webpack/webpack-dev-middleware repo. | ai | |
| dependencies | unvetted-dep:memfs | AI (dependencies): memfs is a well-known in-memory filesystem library that is a standard dependency of webpack-dev-middleware for serving compiled assets; its use is expected and appropriate for this package. | ai | |
| dependencies | unvetted-peer-dep:webpack | AI (dependencies): webpack is the canonical peer dependency for webpack-dev-middleware; this is expected and stable across all versions of this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 8.0.3 | 5 / 37 | |
| 8.0.2 | 5 / 37 | |
| 8.0.1 | 5 / 37 | |
| 8.0.0 | 5 / 37 | |
| 7.4.5 | 6 / 50 | |
| 7.4.4 | 6 / 50 | |
| 7.4.3 | 6 / 52 | |
| 7.4.2 | 6 / 43 | |
| 7.4.1 | 6 / 43 | |
| 7.4.0 | 6 / 43 | |
| 7.3.0 | 6 / 44 | |
| 7.2.1 | 6 / 40 | |
| 7.2.0 | 6 / 40 | |
| 7.1.1 | 6 / 35 | |
| 7.1.0 | 6 / 35 | |
| 6.1.3 | 5 / 33 | |
| 6.1.2 | 5 / 33 | |
| 5.3.4 | 5 / 33 |
v8.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.