webpack-plugin-serve
A Development Server in a Webpack Plugin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Mature package from established publisher; provenance absence is best-practice gap, not security risk. | ai | |
| phantom-deps | phantom-dep:@types/koa | AI (phantom-deps): TypeScript type definitions loaded by convention; standard practice for typed projects. | ai | |
| phantom-deps | phantom-dep:@types/webpack | AI (phantom-deps): TypeScript type definitions loaded by convention; standard practice for typed projects. | ai | |
| phantom-deps | phantom-dep:@types/http-proxy-middleware | AI (phantom-deps): TypeScript type definitions loaded by convention; standard practice for typed projects. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): safe-stable-stringify is a well-known, legitimate utility package. Its addition is consistent with the plugin's purpose of serializing data safely. No malicious indicators. | ai | |
| dependencies | unvetted-dep:onetime | AI (dependencies): onetime is a well-known sindresorhus utility with no malicious history; stable false positive for this package. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 23 / 19 | |
| 1.5.0 | 23 / 19 | |
| 1.4.1 | 23 / 19 | |
| 1.4.0 | 23 / 19 | |
| 1.3.0 | 23 / 19 | |
| 1.2.1 | 23 / 19 | |
| 1.2.0 | 22 / 18 | |
| 1.1.0 | 22 / 17 | |
| 1.0.1 | 22 / 17 | |
| 1.0.0 | 22 / 17 | |
| 0.12.1 | 22 / 20 | |
| 0.12.0 | 22 / 20 | |
| 0.11.0 | 18 / 20 | |
| 0.10.0 | 18 / 20 | |
| 0.9.1 | 18 / 20 | |
| 0.9.0 | 18 / 20 | |
| 0.8.0 | 17 / 20 | |
| 0.7.4 | 20 / 23 | |
| 0.7.3 | 20 / 23 | |
| 0.7.2 | 20 / 23 | |
| 0.7.1 | 20 / 23 | |
| 0.7.0 | 20 / 23 | |
| 0.6.0 | 17 / 20 | |
| 0.5.1 | 17 / 20 | |
| 0.5.0 | 17 / 20 | |
| 0.4.0 | 17 / 20 | |
| 0.3.1 | 17 / 20 | |
| 0.3.0 | 16 / 16 | |
| 0.2.2 | 16 / 16 | |
| 0.2.1 | 16 / 17 | |
| 0.2.0 | 16 / 17 | |
| 0.1.2 | 15 / 17 | |
| 0.1.1 | 15 / 17 | |
| 0.1.0 | 15 / 17 |
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.