@html-eslint/template-parser
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established html-eslint ecosystem package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.64.0 | 2 / 5 | |
| 0.63.0 | 2 / 5 | |
| 0.62.0 | 2 / 5 | |
| 0.61.0 | 2 / 5 | |
| 0.60.0 | 2 / 5 | |
| 0.59.0 | 2 / 5 | |
| 0.58.1 | 2 / 5 | |
| 0.58.0 | 2 / 5 | |
| 0.57.0 | 2 / 5 | |
| 0.56.0 | 2 / 5 | |
| 0.55.0 | 2 / 5 | |
| 0.54.0 | 2 / 5 | |
| 0.53.0 | 2 / 5 | |
| 0.52.0 | 2 / 5 | |
| 0.51.0 | 2 / 5 | |
| 0.50.0 | 2 / 5 | |
| 0.49.0 | 2 / 5 | |
| 0.48.0 | 2 / 5 | |
| 0.47.1 | 2 / 5 | |
| 0.47.0 | 2 / 5 | |
| 0.46.2 | 2 / 5 | |
| 0.46.0 | 1 / 6 | |
| 0.45.0 | 1 / 6 | |
| 0.44.0 | 1 / 6 | |
| 0.43.0 | 1 / 6 | |
| 0.42.0 | 1 / 6 | |
| 0.41.0 | 1 / 6 | |
| 0.40.0 | 1 / 6 | |
| 0.39.0 | 1 / 6 | |
| 0.38.0 | 1 / 6 | |
| 0.37.0 | 1 / 6 | |
| 0.36.0 | 1 / 6 | |
| 0.35.2 | 1 / 6 | |
| 0.35.1 | 1 / 6 | |
| 0.35.0 | 1 / 4 | |
| 0.34.0 | 1 / 4 | |
| 0.33.0 | 1 / 4 | |
| 0.32.0 | 1 / 4 | |
| 0.31.0 | 1 / 4 | |
| 0.30.0 | 1 / 4 | |
| 0.29.0 | 1 / 4 | |
| 0.28.0 | 1 / 4 |
v0.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.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.
v0.41.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.
v0.40.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.
v0.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.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.
v0.37.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.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.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.