@html-eslint/eslint-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
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 | |
| dependencies | unvetted-dep:@html-eslint/parser | AI (dependencies): First-party monorepo package under the same @html-eslint scope; not a third-party risk. | ai | |
| 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 | |
| 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 | |
| dependencies | unvetted-dep:@html-eslint/types | AI (dependencies): First-party monorepo package under the same @html-eslint scope; not a third-party risk. | ai | |
| 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 | |
| dependencies | unvetted-dep:html-standard | AI (dependencies): Small HTML spec utility dependency; consistent with an HTML linting plugin's legitimate needs. | ai | |
| 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 |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.61.0 | 8 / 5 | |
| 0.60.0 | 8 / 5 | |
| 0.59.0 | 8 / 5 | |
| 0.58.1 | 8 / 5 | |
| 0.58.0 | 8 / 5 | |
| 0.57.1 | 8 / 6 | |
| 0.57.0 | 7 / 6 | |
| 0.56.0 | 6 / 6 | |
| 0.55.0 | 6 / 6 | |
| 0.54.2 | 5 / 6 | |
| 0.54.1 | 5 / 6 | |
| 0.54.0 | 5 / 6 | |
| 0.53.0 | 5 / 6 | |
| 0.52.1 | 5 / 6 | |
| 0.52.0 | 5 / 6 | |
| 0.51.0 | 5 / 6 | |
| 0.50.0 | 5 / 6 | |
| 0.49.0 | 5 / 6 | |
| 0.48.0 | 5 / 6 | |
| 0.47.1 | 5 / 6 | |
| 0.47.0 | 5 / 6 | |
| 0.46.2 | 5 / 6 | |
| 0.46.1 | 4 / 7 | |
| 0.46.0 | 4 / 7 | |
| 0.45.0 | 4 / 7 | |
| 0.44.0 | 4 / 7 | |
| 0.43.1 | 4 / 7 | |
| 0.43.0 | 4 / 7 | |
| 0.42.0 | 4 / 7 | |
| 0.41.0 | 4 / 7 | |
| 0.40.3 | 4 / 8 | |
| 0.40.2 | 4 / 8 | |
| 0.40.1 | 3 / 9 | |
| 0.40.0 | 3 / 9 |
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.