@html-eslint/eslint-plugin No license 57 versions

@html-eslint/eslint-plugin

npm Repository Homepage

57

Versions

—

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

yeonjuan-joah

Keywords

eslinteslintplugineslint-pluginhtmlformatterlintaccessibility

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@html-eslint/core	AI (dependencies): First-party monorepo package under the same @html-eslint scope; not a third-party risk.	ai	2026/04/26
dependencies	unvetted-dep:@html-eslint/parser	AI (dependencies): First-party monorepo package under the same @html-eslint scope; not a third-party risk.	ai	2026/04/26
dependencies	unvetted-dep:@html-eslint/template-parser	AI (dependencies): First-party monorepo package under the same @html-eslint scope; not a third-party risk.	ai	2026/04/26
dependencies	unvetted-dep:@html-eslint/template-syntax-parser	AI (dependencies): First-party monorepo package under the same @html-eslint scope; not a third-party risk.	ai	2026/04/26
dependencies	unvetted-dep:@html-eslint/types	AI (dependencies): First-party monorepo package under the same @html-eslint scope; not a third-party risk.	ai	2026/04/26
dependencies	unvetted-dep:@rviscomi/capo.js	AI (dependencies): Legitimate library by Rick Viscomi (Google engineer) for HTML head element ordering; well-known in the web performance community.	ai	2026/04/26
dependencies	unvetted-dep:html-standard	AI (dependencies): Small HTML spec utility dependency; consistent with an HTML linting plugin's legitimate needs.	ai	2026/04/26
phantom-deps	phantom-dep:@html-eslint/template-syntax-parser	AI (phantom-deps): Same-scope monorepo package; may be used indirectly. Not a phantom dependency risk.	ai	2026/04/26

Versions (showing 57 of 57)

Version	Deps	Published
0.64.0	8 / 5	2026-07-10
0.63.0	8 / 5	2026-06-27
0.62.0	8 / 5	2026-06-09
0.61.0	8 / 5	2026-05-24
0.60.0	8 / 5	2026-04-29
0.59.0	8 / 5	2026-04-05
0.58.1	8 / 5	2026-03-05
0.58.0	8 / 5	2026-03-04
0.57.1	8 / 6	2026-02-25
0.57.0	7 / 6	2026-02-23
0.56.0	6 / 6	2026-02-20
0.55.0	6 / 6	2026-02-14
0.54.2	5 / 6	2026-01-31
0.54.1	5 / 6	2026-01-31
0.54.0	5 / 6	2026-01-26
0.53.0	5 / 6	2026-01-15
0.52.1	5 / 6	2025-12-30
0.52.0	5 / 6	2025-12-19
0.51.0	5 / 6	2025-12-13
0.50.0	5 / 6	2025-11-27
0.49.0	5 / 6	2025-11-20
0.48.0	5 / 6	2025-11-07
0.47.1	5 / 6	2025-11-04
0.47.0	5 / 6	2025-09-28
0.46.2	5 / 6	2025-09-03
0.46.1	4 / 7	2025-08-26
0.46.0	4 / 7	2025-08-24
0.45.0	4 / 7	2025-08-12
0.44.0	4 / 7	2025-07-31
0.43.1	4 / 7	2025-07-24
0.43.0	4 / 7	2025-07-19
0.42.0	4 / 7	2025-06-22
0.41.0	4 / 7	2025-05-26
0.40.3	4 / 8	2025-05-11
0.40.2	4 / 8	2025-05-09
0.40.1	3 / 9	2025-05-08
0.40.0	3 / 9	2025-05-03
0.39.0	2 / 8	2025-04-17
0.38.1	2 / 8	2025-04-06
0.38.0	2 / 8	2025-04-05
0.37.0	2 / 8	2025-03-25
0.36.0	2 / 8	2025-03-17
0.35.2	2 / 8	2025-03-06
0.35.1	2 / 8	2025-03-05
0.35.0	2 / 7	2025-02-14
0.34.0	2 / 7	2025-01-31
0.33.1	1 / 6	2025-01-24
0.33.0	1 / 6	2025-01-21
0.32.0	1 / 6	2025-01-02
0.31.1	1 / 6	2024-12-12
0.31.0	1 / 6	2024-12-10
0.30.0	1 / 6	2024-12-03
0.29.0	1 / 6	2024-12-01
0.28.0	1 / 7	2024-12-01
0.27.0	0 / 5	2024-09-15
0.26.0	0 / 5	2024-08-06
0.25.0	0 / 5	2024-06-20

v0.64.0

1 finding

LOW No provenance attestation provenance

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

v0.63.0

1 finding

LOW No provenance attestation provenance

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

v0.62.0

1 finding

LOW No provenance attestation provenance

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

v0.61.0

1 finding

LOW No provenance attestation provenance

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

v0.47.0

1 finding

LOW No provenance attestation provenance

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

v0.46.2

1 finding

LOW No provenance attestation provenance

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

v0.46.1

1 finding

LOW No provenance attestation provenance

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

v0.46.0

1 finding

LOW No provenance attestation provenance

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

v0.45.0

1 finding

LOW No provenance attestation provenance

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

v0.44.0

1 finding

LOW No provenance attestation provenance

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

v0.43.1

1 finding

LOW No provenance attestation provenance

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

v0.43.0

1 finding

LOW No provenance attestation provenance

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

v0.42.0

1 finding

LOW No provenance attestation provenance

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

v0.41.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.

v0.40.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.

v0.40.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.

v0.40.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.

v0.40.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.

v0.39.0

1 finding

LOW No provenance attestation provenance

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

v0.38.1

1 finding

LOW No provenance attestation provenance

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

v0.38.0

1 finding

LOW No provenance attestation provenance

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

v0.37.0

1 finding

LOW No provenance attestation provenance

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

v0.36.0

1 finding

LOW No provenance attestation provenance

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

v0.35.2

1 finding

LOW No provenance attestation provenance

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

v0.35.1

1 finding

LOW No provenance attestation provenance

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

v0.35.0

1 finding

LOW No provenance attestation provenance

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

v0.34.0

1 finding

LOW No provenance attestation provenance

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

v0.33.1

1 finding

LOW No provenance attestation provenance

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

v0.33.0

1 finding

LOW No provenance attestation provenance

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

v0.32.0

1 finding

LOW No provenance attestation provenance

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

v0.31.1

1 finding

LOW No provenance attestation provenance

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

v0.31.0

1 finding

LOW No provenance attestation provenance

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

v0.30.0

1 finding

LOW No provenance attestation provenance

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

v0.29.0

1 finding

LOW No provenance attestation provenance

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

v0.28.0

1 finding

LOW No provenance attestation provenance

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

v0.27.0

1 finding

LOW No provenance attestation provenance

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

v0.26.0

1 finding

LOW No provenance attestation provenance

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

v0.25.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.