image-min
Minify GIF, JPEG and PNG images
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): image-min invokes native image compression binaries (gifsicle, jpegtran, optipng) via child_process.spawn — this is the core mechanism of the package, not malicious. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is declared as a dependency but not in the main file; minor packaging artifact in a 12-year-old package, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Package is over 12 years old; provenance attestation predates the tooling. Not a meaningful risk signal for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.4.5 | 14 / 1 | |
| 0.4.4 | 10 / 1 | |
| 0.4.2 | 10 / 1 | |
| 0.4.1 | 10 / 1 | |
| 0.4.0 | 10 / 1 | |
| 0.3.2 | 7 / 2 | |
| 0.3.0 | 8 / 2 | |
| 0.2.3 | 12 / 2 | |
| 0.2.2 | 12 / 2 | |
| 0.2.1 | 11 / 2 | |
| 0.2.0 | 10 / 2 | |
| 0.1.4 | 6 / 3 | |
| 0.1.3 | 7 / 3 | |
| 0.1.2 | 8 / 1 | |
| 0.1.1 | 8 / 1 | |
| 0.1.0 | 8 / 1 |
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.