Mediamodifier
Mediamodifier's feed is a template catalog: one mockup per entry, several a day.
Comparison · Design
libvips vs OpenEXR
A side-by-side editorial comparison of libvips and OpenEXR — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:memory-safety
libvips vs OpenEXR: at a glance
What is libvips?
libvips 8.18 opened up UltraHDR and Oklab, then spent months closing memory bugs.
The feed tracks release candidates only. The 8.18 line added UltraHDR load and save, Oklab and Oklch colourspaces, raw camera loading through libraw, and gainmap plumbing through thumbnail and dzsave. The most recent tag, 8.18.3-rc1, is a different kind of release: roughly two dozen fixes for out-of-bounds reads, heap overflows and null dereferences across the jp2k, HEIF, Radiance, Magick and PPM loaders.
What is OpenEXR?
A second IDManifest flaw lands two weeks after OpenEXR's forty-CVE sweep
OpenEXR's recent history is dominated by security response. On 2026-08-05 three branches were tagged within two minutes — v3.4.14, v3.3.13 and v3.2.11, fixing 15, 15 and 10 CVEs from one fuzzing and audit campaign, all memory corruption reachable by opening a crafted .exr file. Two weeks later v3.4.15 and v3.3.14 fix two further memory-allocation issues, this time confined to the code that decodes the idmanifest attribute, with CVEs requested but not yet assigned. The 3.4 tag also carries a missing Windows export and reduced compiler warnings in example code.
libvips vs OpenEXR: editorial side-by-side
libvips
0.0DESIGN
libvips 8.18 opened up UltraHDR and Oklab, then spent months closing memory bugs.
◆ Current state
The feed tracks release candidates only. The 8.18 line added UltraHDR load and save, Oklab and Oklch colourspaces, raw camera loading through libraw, and gainmap plumbing through thumbnail and dzsave. The most recent tag, 8.18.3-rc1, is a different kind of release: roughly two dozen fixes for out-of-bounds reads, heap overflows and null dereferences across the jp2k, HEIF, Radiance, Magick and PPM loaders.
◆ Where it's heading
The arc runs from capability expansion to hardening. Having taken on more untrusted input formats, libvips is now paying the cost of that surface in memory-safety fixes, several credited to external fuzzing and security researchers. Format reach and attack surface are growing together.
◆ Prediction
With 8.18.3-rc1 dominated by loader bounds checks, the next tags are likely to continue as patch-level hardening on the 8.18 line rather than open a new format frontier.
OpenEXR
5.0DESIGN
A second IDManifest flaw lands two weeks after OpenEXR's forty-CVE sweep
◆ Current state
OpenEXR's recent history is dominated by security response. On 2026-08-05 three branches were tagged within two minutes — v3.4.14, v3.3.13 and v3.2.11, fixing 15, 15 and 10 CVEs from one fuzzing and audit campaign, all memory corruption reachable by opening a crafted .exr file. Two weeks later v3.4.15 and v3.3.14 fix two further memory-allocation issues, this time confined to the code that decodes the idmanifest attribute, with CVEs requested but not yet assigned. The 3.4 tag also carries a missing Windows export and reduced compiler warnings in example code.
◆ Where it's heading
The pattern is now established: findings arrive from a continuing fuzzing effort and are patched simultaneously across every supported stream, with the release notes written to tell integrators precisely which code paths are reachable. The narrowing scope is the useful signal — August's first batch spanned the C++ libraries, the command-line tools and the Python bindings, while this one touches only idmanifest decoding and explicitly states other code is unaffected even on files carrying the attribute. Both new tags are release candidates dated ahead of their tagging, and the 3.3 backport reuses the 3.4 note verbatim, down to naming v3.4.15 in its own body.
◆ Prediction
Expect the requested CVEs to be assigned identifiers and the two RCs to be promoted to final tags, with a matching 3.2 backport if the idmanifest code is present in that stream. Further attribute-parser findings are likely while the fuzzing campaign continues.
Alternatives to libvips and OpenEXR
Other Design products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either libvips or OpenEXR.
Spectra
Spectra Blocks spends its first six weeks patching what 1.0 shipped.
Storybook
Storybook is turning its component workshop into a tool surface agents can call.
Picsart
Picsart bolts on every new video model within days — WAN 3.0 pushes single takes to 30 seconds.
Visme
Visme extended past documents into no-code microsites, then hardened the layout and brand layer.
Godot Engine
Godot 4.7.2 lands as pure patch traffic, with the 4.6 branch still taking fixes alongside it.
See all libvips alternatives → · See all OpenEXR alternatives →
Recent activity from libvips and OpenEXR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10h agoOpenEXR3.3.14 backports the IDManifest memory fixes to the 3.3 stream
- 11h agoOpenEXR3.4.15 fixes two IDManifest memory-allocation flaws
- 14d agoOpenEXR3.4.14 fixes 15 CVEs found by fuzzing the .exr parser
- 14d agoOpenEXR3.3.13 backports the same 15 CVE fixes to the 3.3 stream
- 14d agoOpenEXR3.2.11 carries 10 of the CVE fixes to the oldest supported stream
- 2mo agoOpenEXR3.3.12-rc updates CI install scripts
- 2mo agolibvips8.18.3-rc1 hardens image loaders against out-of-bounds reads
- 8mo agolibvipsThird 8.18.0 release candidate
- 8mo agolibvipsSecond 8.18.0 release candidate
- 8mo agolibvips8.18 adds UltraHDR, Oklab colour and raw camera loading ⚡
Frequently asked questions
What is the difference between libvips and OpenEXR?
Both compete on the same themes — memory-safety — within Design. OpenEXR is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is libvips better than OpenEXR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenEXR is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Design products to evaluate alongside.
What are the best alternatives to libvips?
Top libvips alternatives in Design are ranked by recent ship velocity. Browse the "libvips alternatives" section above for the current picks, or visit /alternatives/libvips for the full list with editorial commentary on each.
What are the best alternatives to OpenEXR?
Top OpenEXR alternatives in Design are ranked by recent ship velocity. Browse the "OpenEXR alternatives" section above for the current picks, or visit /alternatives/openexr for the full list with editorial commentary on each.