grunt-contrib-htmlmin
Minify HTML
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-minifier | AI (dependencies): html-minifier is the core dependency this package wraps; its use is expected and appropriate for all versions of grunt-contrib-htmlmin. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence is expected for this long-established Grunt plugin and not a security concern. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from vladikoff to xhmikosr within the Grunt team in 2019. xhmikosr has 687 approved packages and a long track record; not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with the maintainer transition period. Grunt ecosystem naturally sees slower release cadence; no malicious activity indicated. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 3 / 5 | |
| 2.4.0 | 3 / 5 | |
| 2.2.0 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.5.0 | 3 / 5 | |
| 1.4.0 | 3 / 5 | |
| 1.3.0 | 3 / 5 | |
| 1.2.0 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.0 | 3 / 6 | |
| 0.6.0 | 3 / 6 | |
| 0.5.0 | 3 / 6 | |
| 0.4.0 | 3 / 6 | |
| 0.3.0 | 3 / 5 | |
| 0.2.0 | 4 / 5 | |
| 0.1.3 | 2 / 5 | |
| 0.1.2 | 2 / 5 | |
| 0.1.1 | 2 / 5 | |
| 0.1.0 | 3 / 5 |
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-04. This could indicate a legitimate maintainer transition or an account compromise.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.