gulp-less
Less for Gulp
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): Legitimate transfer to contra (core gulp maintainer) under the gulp-community GitHub org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old maintainer cleanup during transfer to gulp-community org; contra is the established steward. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Major version bump after long stability period; normal for mature gulp plugins transferred to gulp-community. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 6 / 4 | |
| 4.0.1 | 7 / 4 | |
| 4.0.0 | 7 / 4 | |
| 3.5.0 | 7 / 4 | |
| 3.4.0 | 7 / 4 | |
| 3.3.2 | 6 / 3 | |
| 3.3.1 | 6 / 3 | |
| 3.3.0 | 6 / 3 | |
| 3.2.0 | 6 / 3 | |
| 3.1.0 | 6 / 3 | |
| 3.0.5 | 6 / 3 | |
| 3.0.4 | 6 / 3 | |
| 3.0.3 | 6 / 3 | |
| 3.0.2 | 6 / 3 | |
| 3.0.1 | 6 / 3 | |
| 3.0.0 | 6 / 3 | |
| 2.0.3 | 6 / 3 | |
| 2.0.2 | 6 / 3 | |
| 2.0.1 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.3.9 | 6 / 3 | |
| 1.3.8 | 6 / 3 | |
| 1.3.7 | 6 / 3 | |
| 1.3.6 | 6 / 3 | |
| 1.3.5 | 6 / 3 | |
| 1.3.4 | 6 / 3 | |
| 1.3.3 | 6 / 3 | |
| 1.3.2 | 6 / 3 | |
| 1.3.1 | 6 / 3 | |
| 1.3.0 | 6 / 3 | |
| 1.2.4 | 4 / 3 | |
| 1.2.3 | 4 / 3 | |
| 1.2.2 | 4 / 3 | |
| 1.2.1 | 4 / 3 | |
| 1.2.0 | 4 / 3 | |
| 1.1.10 | 4 / 3 | |
| 1.1.8 | 4 / 2 | |
| 1.1.7 | 4 / 2 | |
| 1.1.6 | 4 / 2 | |
| 1.1.5 | 4 / 2 | |
| 1.1.4 | 4 / 2 | |
| 1.1.3 | 4 / 2 | |
| 1.1.1 | 4 / 2 | |
| 1.1.0 | 4 / 2 | |
| 1.0.2 | 4 / 2 | |
| 1.0.1 | 4 / 2 | |
| 1.0.0 | 4 / 2 | |
| 0.0.3 | 5 / 2 | |
| 0.0.2 | 5 / 2 | |
| 0.0.1 | 5 / 1 | |
| 0.0.0 | 5 / 1 |
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-16. 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.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.