html-webpack-plugin MIT 25 versions

html-webpack-plugin

npm Repository Homepage

Simplifies creation of HTML files to serve your webpack bundles

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

jantimonampedandwiredmastilverthelarkinnevilebottnawi

Keywords

webpackpluginhtmlhtml-webpack-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/tapable	AI (phantom-deps): TypeScript type definitions are conventionally loaded and used for type checking; stable pattern for this package.	ai	2026/04/23
phantom-deps	phantom-dep:@types/webpack	AI (phantom-deps): TypeScript type definitions are conventionally loaded and used for type checking; stable pattern for this package.	ai	2026/04/23
phantom-deps	phantom-dep:@types/html-minifier-terser	AI (phantom-deps): TypeScript type definitions are conventionally loaded and used for type checking; stable pattern for this package.	ai	2026/04/23

Versions (showing 25 of 25)

Version	Deps	Published
5.6.6	5 / 27	2026-01-16
5.6.5	5 / 26	2025-11-18
5.5.0	5 / 19	2021-10-25
5.4.0	5 / 19	2021-10-15
5.3.2	5 / 19	2021-06-22
5.3.1	5 / 19	2021-03-09
5.3.0	5 / 20	2021-03-07
5.2.0	6 / 20	2021-02-19
5.1.0	6 / 21	2021-02-12
5.0.0	6 / 21	2021-02-03
4.5.2	9 / 20	2021-02-18
4.5.1	9 / 20	2021-01-03
4.5.0	9 / 20	2020-09-21
4.4.1	9 / 20	2020-08-30
4.4.0	9 / 20	2020-08-30
4.3.0	9 / 20	2020-04-30
4.2.2	9 / 20	2020-04-30
4.2.1	9 / 20	2020-04-28
4.2.0	9 / 20	2020-04-09
4.1.0	9 / 20	2020-04-09
4.0.4	9 / 20	2020-04-01
4.0.3	9 / 20	2020-03-28
4.0.2	6 / 22	2020-03-26
4.0.1	6 / 22	2020-03-23
4.0.0	6 / 22	2020-03-23

v5.6.6

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.

v5.6.5

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.

v5.5.0

1 finding

LOW No provenance attestation provenance

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

v5.4.0

1 finding

LOW No provenance attestation provenance

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

v5.3.2

1 finding

LOW No provenance attestation provenance

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

v5.3.1

1 finding

LOW No provenance attestation provenance

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

v5.3.0

1 finding

LOW No provenance attestation provenance

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

v5.2.0

1 finding

LOW No provenance attestation provenance

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

v5.1.0

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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

v4.5.2

1 finding

LOW No provenance attestation provenance

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

v4.5.1

1 finding

LOW No provenance attestation provenance

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

v4.4.1

1 finding

LOW No provenance attestation provenance

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

v4.4.0

1 finding

LOW No provenance attestation provenance

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

v4.3.0

1 finding

LOW No provenance attestation provenance

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

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.4

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.

v4.0.3

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.

v4.0.2

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.

v4.0.1

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.

v4.0.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.