@html-eslint/cli
HTML-ESLint CLI
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @html-eslint/cli; Levenshtein match to 'joi' is a false positive with no brand impersonation. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load a user-specified ESLint config file — standard CLI pattern, not arbitrary code execution risk. | ai |
Versions (showing 80 of 80)
| Version | Deps | Published |
|---|---|---|
| 0.64.0 | 6 / 0 | |
| 0.63.0 | 6 / 0 | |
| 0.62.0 | 6 / 0 | |
| 0.61.0 | 6 / 0 | |
| 0.60.0 | 6 / 0 | |
| 0.59.0 | 6 / 0 | |
| 0.58.1 | 6 / 0 | |
| 0.58.0 | 6 / 0 | |
| 0.57.1 | 6 / 0 | |
| 0.57.0 | 6 / 0 | |
| 0.56.0 | 6 / 0 | |
| 0.55.0 | 6 / 0 | |
| 0.54.2 | 6 / 0 | |
| 0.54.1 | 6 / 0 | |
| 0.54.0 | 6 / 0 | |
| 0.53.0 | 6 / 0 | |
| 0.52.1 | 6 / 0 | |
| 0.52.0 | 6 / 0 | |
| 0.51.0 | 6 / 0 | |
| 0.50.0 | 6 / 0 | |
| 0.49.0 | 6 / 0 | |
| 0.48.0 | 6 / 0 | |
| 0.47.1 | 6 / 0 | |
| 0.47.0 | 6 / 0 | |
| 0.46.2 | 6 / 0 | |
| 0.46.1 | 6 / 0 | |
| 0.46.0 | 6 / 0 | |
| 0.45.0 | 6 / 0 | |
| 0.44.0 | 6 / 0 | |
| 0.43.1 | 6 / 0 | |
| 0.43.0 | 6 / 0 | |
| 0.42.0 | 6 / 0 | |
| 0.41.0 | 6 / 0 | |
| 0.40.3 | 6 / 0 | |
| 0.40.2 | 6 / 0 | |
| 0.40.1 | 6 / 0 | |
| 0.40.0 | 6 / 0 | |
| 0.39.0 | 6 / 0 | |
| 0.38.1 | 6 / 0 | |
| 0.38.0 | 6 / 0 | |
| 0.37.0 | 6 / 0 | |
| 0.36.0 | 6 / 0 | |
| 0.35.2 | 6 / 0 | |
| 0.35.1 | 6 / 0 | |
| 0.35.0 | 6 / 0 | |
| 0.34.0 | 6 / 0 | |
| 0.33.1 | 6 / 0 | |
| 0.33.0 | 6 / 0 | |
| 0.32.0 | 6 / 0 | |
| 0.31.1 | 6 / 0 | |
| 0.31.0 | 6 / 0 | |
| 0.30.0 | 6 / 0 | |
| 0.29.0 | 6 / 0 | |
| 0.28.0 | 6 / 0 | |
| 0.27.0 | 6 / 0 | |
| 0.26.0 | 6 / 0 | |
| 0.25.0 | 6 / 0 | |
| 0.24.1 | 6 / 0 | |
| 0.24.0 | 6 / 0 | |
| 0.23.1 | 6 / 0 | |
| 0.23.0 | 6 / 0 | |
| 0.22.0 | 6 / 0 | |
| 0.21.0 | 6 / 0 | |
| 0.20.0 | 6 / 0 | |
| 0.19.1 | 6 / 0 | |
| 0.19.0 | 6 / 0 | |
| 0.18.0 | 6 / 0 | |
| 0.17.2 | 6 / 0 | |
| 0.17.1 | 6 / 0 | |
| 0.17.0 | 6 / 0 | |
| 0.16.0 | 6 / 0 | |
| 0.15.0 | 6 / 0 | |
| 0.14.1 | 6 / 0 | |
| 0.14.0 | 6 / 0 | |
| 0.13.2 | 6 / 0 | |
| 0.13.1 | 6 / 0 | |
| 0.13.0 | 6 / 0 | |
| 0.12.0 | 6 / 0 | |
| 0.11.1 | 6 / 0 | |
| 0.11.0 | 6 / 0 |
v0.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.