htmlhint
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
Keywords
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.9.2 | 8 / 17 | |
| 1.9.1 | 8 / 17 | |
| 1.9.0 | 8 / 17 | |
| 1.8.1 | 8 / 17 | |
| 1.8.0 | 8 / 17 | |
| 1.7.1 | 8 / 17 | |
| 1.7.0 | 8 / 18 | |
| 1.6.3 | 8 / 18 | |
| 1.6.2 | 8 / 18 | |
| 1.6.1 | 8 / 18 | |
| 1.6.0 | 8 / 18 | |
| 1.5.1 | 9 / 19 | |
| 1.5.0 | 9 / 19 | |
| 1.4.0 | 8 / 19 | |
| 1.3.0 | 8 / 19 | |
| 1.2.0 | 8 / 19 | |
| 1.1.4 | 8 / 24 | |
| 1.1.3 | 8 / 24 | |
| 1.1.2 | 8 / 25 | |
| 1.1.1 | 8 / 25 | |
| 1.1.0 | 8 / 26 | |
| 1.0.0 | 8 / 33 |
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.