gulp-rename
Rename files
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): Publisher change to fractal (core gulp ecosystem maintainer) occurred in 2015; legitimate transfer within the gulp org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): contra, shinnn, fractal are well-known gulp ecosystem maintainers; legitimate team expansion from 2015. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2015, before Sigstore/provenance existed. Expected for this era. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Package uses files whitelist to ship only index.js; size drop reflects cleanup of previously included test/extra files. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 0 / 7 | |
| 2.0.0 | 0 / 7 | |
| 1.4.0 | 0 / 8 | |
| 1.3.0 | 0 / 8 | |
| 1.2.3 | 0 / 8 | |
| 1.2.2 | 0 / 7 | |
| 1.2.0 | 0 / 5 | |
| 1.1.0 | 1 / 4 | |
| 1.0.0 | 1 / 4 | |
| 0.2.2 | 1 / 4 | |
| 0.2.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 |
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-26. 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
2 findingsThis version was published by a different npm account than previous versions on 2018-05-15. 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.
v1.2.2
2 findingsThis version was published by a different npm account than previous versions on 2015-04-02. 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.
v1.2.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.