grunt-contrib-less
Compile LESS files to CSS
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 | publisher-changed | AI (provenance): vladikoff is a recognized Grunt team member with a strong track record; the transition from xhmikosr to vladikoff in 2018 is a documented legitimate maintainer change within the gruntjs org. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 4 / 6 | |
| 2.1.0 | 4 / 6 | |
| 2.0.0 | 4 / 6 | |
| 1.4.1 | 4 / 6 | |
| 1.4.0 | 4 / 6 | |
| 1.3.0 | 4 / 6 | |
| 1.2.0 | 4 / 7 | |
| 1.1.0 | 4 / 7 | |
| 1.0.1 | 4 / 6 | |
| 1.0.0 | 4 / 6 | |
| 0.12.0 | 5 / 6 | |
| 0.11.4 | 5 / 6 | |
| 0.11.3 | 5 / 6 | |
| 0.11.2 | 5 / 6 | |
| 0.11.1 | 5 / 6 | |
| 0.11.0 | 5 / 6 | |
| 0.10.0 | 3 / 5 | |
| 0.9.0 | 3 / 5 | |
| 0.8.3 | 2 / 5 | |
| 0.8.2 | 2 / 5 | |
| 0.8.1 | 2 / 5 | |
| 0.8.0 | 2 / 5 | |
| 0.7.0 | 2 / 5 | |
| 0.6.5 | 2 / 5 | |
| 0.6.4 | 2 / 5 | |
| 0.6.3 | 2 / 5 | |
| 0.6.2 | 1 / 5 | |
| 0.6.1 | 1 / 5 | |
| 0.6.0 | 1 / 5 | |
| 0.5.2 | 1 / 5 | |
| 0.5.1 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.3.2 | 2 / 2 | |
| 0.3.1 | 2 / 2 | |
| 0.3.0 | 2 / 2 | |
| 0.2.2 | 2 / 2 | |
| 0.2.1 | 2 / 2 | |
| 0.2.0 | 2 / 2 | |
| 0.1.0 | 2 / 2 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-05-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.