← Home

imagemin-optipng

Imagemin plugin for OptiPNG

19
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

1000chbradbariskevvanothingismagickshinnnsindresorhusxhmikosr

Keywords

imageminplugincompressimageminifyoptimizeoptipngpng

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): 1000ch is a long-standing npm publisher (4340 days, 304 approved packages) within the imagemin org; transfer from sindresorhus is a documented legitimate handoff pattern for this ecosystem. ai

Versions (showing 19 of 19)

Version Deps Published
8.0.0 3 / 2
7.1.0 3 / 2
7.0.0 3 / 2
6.0.0 3 / 2
5.2.1 3 / 3
5.2.0 3 / 3
5.1.1 3 / 3
5.1.0 3 / 3
5.0.0 3 / 3
4.3.0 4 / 2
4.2.0 4 / 2
4.1.0 4 / 2
4.0.0 4 / 2
3.1.0 4 / 2
3.0.0 4 / 2
2.0.1 4 / 2
2.0.0 4 / 2
1.0.0 3 / 3
0.1.0 4 / 2

v8.0.0

2 findings
HIGH Publisher changed: sindresorhus → 1000ch (on 2020-05-24) provenance

This version was published by a different npm account than previous versions on 2020-05-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: 1000ch → sindresorhus (on 2019-05-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-25. This could indicate a legitimate maintainer transition or an account compromise.