Roadmap

Codec implementation order came from a single rolling-year npm downloads window rather than subjective priority.

Phase	Compatibility target	Status
0	Core pipeline and Oxipng prototype	Complete
1	imagemin-svgo	Complete
2	imagemin-gifsicle and OptiPNG	Complete
3	imagemin-pngquant	Complete
4	imagemin-mozjpeg and jpegtran	Complete
5	imagemin-webp	Complete
6	imagemin-avif	Complete

Every codec phase includes a codec ADR, real corpus, Rust adapter, N-API tests, JavaScript compatibility contract, platform smoke tests, benchmarks, and a public compatibility table.

Current focus: post-stable hardening

0.1.0 was published on August 19, 2026. Its release evidence includes:

1. all 35 npm packages under latest with integrity, signatures, and provenance;
2. the immutable tag and GitHub Release contain SBOM, OpenVEX, notices, GPL source, build materials, and recovery assets;
3. all eight native targets passed fresh installation and every-codec smoke;
4. default-without-Sharp, explicit sharp@0.35.3, and browser WASM paths passed registry fresh-install verification;
5. @imagemin-rs/wasm completed bootstrap and trusted-publisher setup.

The trial clock started at 2026-07-30 06:29 +08:00 and the 14-day period ended at 2026-08-13 06:29 +08:00 without a P0/P1. External feedback remains welcome but is not a release-count gate; technical coverage comes from the mandatory eight-platform and browser smoke matrix. See the historical ledger in Stable Public Trial.

The immediate maintenance track hardens fuzz-discovered resource limits, recoverable registry verification, and stable installation guidance before new runtime features begin.

Stable 0.1 scope

The maintainer selected the conservative distribution model:

1. Sharp is an exact optional peer, so AVIF is opt-in and the default install does not distribute the Sharp/libvips stack;
2. every GPL Gifsicle/pngquant platform package carries matching source and build materials, in addition to release-wide backup assets;
3. the browser package remains memory-only with GIF, PNG, and SVG profiles;
4. AVIF 10/12-bit, new codecs, and OS-level isolation stay outside 0.1.

These boundaries shipped in 0.1.0. The canonical internal gate table is the 1.0 release plan.

Planned post-stable tracks

Track	First deliverable
Browser runtime ergonomics	First-class Worker client, batch scheduling, and progress/cancel events
WASM capability	Evaluate more permissively licensed codecs and streaming-friendly APIs
AVIF and color	Permissive native profile plus 10/12-bit, HDR, and color contracts
Runtime isolation	Stronger hard cancellation and OS-level CPU/RSS/process controls
Quality evidence	Larger visual/corrupt-input corpora and longer performance histories
Reproducibility	Compare rebuilt sidecar binaries where upstream toolchains permit it

Each track requires a separate public contract and evidence plan. It does not retroactively change the stable 0.1.0 contract.

The first browser-runtime milestone is bounded by the Browser Worker plan.