imagemin-gifsicle
Imagemin plugin for Gifsicle
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 maintainer transition from kevva to 1000ch (established publisher, 318 approved packages). Change occurred in 2018 within the imagemin org. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2018 before Sigstore provenance was available; expected for packages of this era. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): xhmikosr is a known imagemin org contributor; addition is consistent with the project's community maintainer model, not a takeover signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): execa is a sindresorhus-authored, widely-trusted package replacing exec-buffer for subprocess execution — a routine modernization, not a suspicious dependency. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 3 / 3 | |
| 6.0.1 | 3 / 3 | |
| 6.0.0 | 3 / 3 | |
| 5.2.0 | 3 / 3 | |
| 5.1.0 | 3 / 3 | |
| 5.0.1 | 3 / 3 | |
| 5.0.0 | 3 / 3 | |
| 4.2.0 | 3 / 2 | |
| 4.1.0 | 3 / 2 | |
| 4.0.0 | 3 / 2 | |
| 3.1.0 | 3 / 2 | |
| 3.0.0 | 3 / 2 | |
| 2.0.1 | 3 / 2 | |
| 2.0.0 | 3 / 2 | |
| 1.0.0 | 3 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.1.0 | 4 / 2 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
2 findings[Accepted risk] Package 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-11-02. This could indicate a legitimate maintainer transition or an account compromise.
v6.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-10-31. 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.