imagemin-jpegtran
jpegtran imagemin plugin
18
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
sindresorhus
Keywords
compressimageimageminpluginimgjpegjpegtranjpgminifyoptimize
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): sindresorhus is the imagemin org founder and a top-tier trusted publisher; taking over imagemin-jpegtran is consistent with their known role in the ecosystem. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainers reflects imagemin org consolidation under sindresorhus, not a hostile takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by sindresorhus modernizing the package (ESM, Node 18+) is a known pattern for imagemin ecosystem packages, not a takeover indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (execa, file-type, image-dimensions, uint8array-extras) are all sindresorhus-maintained or well-known packages replacing older equivalents in a modernization effort. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 5 / 4 | |
| 7.0.0 | 3 / 3 | |
| 6.0.0 | 3 / 4 | |
| 5.0.2 | 3 / 4 | |
| 5.0.1 | 3 / 4 | |
| 5.0.0 | 3 / 3 | |
| 4.3.2 | 3 / 5 | |
| 4.3.1 | 3 / 4 | |
| 4.3.0 | 3 / 4 | |
| 4.2.0 | 3 / 4 | |
| 4.1.0 | 3 / 4 | |
| 4.0.0 | 3 / 4 | |
| 3.1.1 | 3 / 4 | |
| 3.1.0 | 3 / 4 | |
| 3.0.0 | 3 / 4 | |
| 2.0.0 | 3 / 2 | |
| 1.0.0 | 3 / 2 | |
| 0.1.0 | 4 / 2 |
v8.0.0
2 findings
HIGH
Publisher changed: 1000ch → sindresorhus (on 2024-09-25)
provenance
This version was published by a different npm account than previous versions on 2024-09-25. 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.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.