gulp-util
Utility functions for gulp plugins
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from Fractal org to phated (Blaine Bublitz), core gulp maintainer. Well-documented handoff. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2015, before Sigstore provenance existed. Stable for this package version. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fancy-log, gulplog, has-gulplog are all gulpjs ecosystem packages adding logging support. Legitimate additions. | ai | |
| dependencies | unvetted-dep:gulplog | AI (dependencies): gulplog is a core gulp ecosystem package from the gulpjs org; a natural and expected dependency for gulp-util. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): contra is a known gulp/gulpjs org member; this is a legitimate team addition, not a suspicious takeover. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 3.0.8 | 18 / 10 | |
| 3.0.7 | 18 / 10 | |
| 3.0.6 | 15 / 10 | |
| 3.0.5 | 15 / 10 | |
| 3.0.4 | 15 / 10 | |
| 3.0.3 | 15 / 10 | |
| 3.0.2 | 13 / 10 | |
| 3.0.1 | 9 / 10 | |
| 3.0.0 | 9 / 10 | |
| 2.2.20 | 8 / 10 | |
| 2.2.19 | 8 / 10 | |
| 2.2.18 | 8 / 10 | |
| 2.2.17 | 8 / 10 | |
| 2.2.16 | 8 / 10 | |
| 2.2.15 | 8 / 10 | |
| 2.2.14 | 8 / 10 | |
| 2.2.13 | 8 / 10 | |
| 2.2.12 | 8 / 10 | |
| 2.2.11 | 8 / 10 | |
| 2.2.10 | 8 / 10 | |
| 2.2.9 | 8 / 4 | |
| 2.2.8 | 7 / 4 | |
| 2.2.7 | 6 / 5 | |
| 2.2.6 | 7 / 4 | |
| 2.2.5 | 6 / 4 | |
| 2.2.3 | 6 / 4 | |
| 2.2.2 | 5 / 4 | |
| 2.2.1 | 5 / 4 | |
| 2.2.0 | 5 / 4 | |
| 2.1.4 | 4 / 4 | |
| 2.1.3 | 4 / 4 | |
| 2.1.2 | 3 / 3 | |
| 2.1.1 | 3 / 3 | |
| 2.0.0 | 3 / 2 | |
| 1.3.0 | 3 / 2 | |
| 1.2.0 | 3 / 2 | |
| 1.1.1 | 3 / 2 | |
| 1.1.0 | 3 / 2 | |
| 1.0.0 | 0 / 2 | |
| 0.0.1 | 0 / 2 |
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
2 findingsThis version was published by a different npm account than previous versions on 2015-10-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.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package 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.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.