@web/dev-server-core
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): Legit CI/CD transition to attested GitHub Actions publish for official modernweb-dev package. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): @types/ws is a runtime dep for TS consumers; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/koa | AI (phantom-deps): @types/koa is a runtime dep for TS consumers; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): mime-types referenced in config files per analyzer note; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 18 / 8 | |
| 0.7.5 | 18 / 8 | |
| 0.7.4 | 18 / 8 | |
| 0.7.3 | 18 / 8 | |
| 0.7.2 | 18 / 8 |
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. 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.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.