← Back to home
Comparison · Design

OpenEXR vs systemfonts

A side-by-side editorial comparison of OpenEXR and systemfonts — release velocity, themes, recent moves, and the top alternatives to consider.

OpenEXR vs systemfonts: at a glance

FeatureOpenEXRsystemfonts
SectorDesignDesign
Velocity score5.00.0
Sparks · 30d00
Top themesimage-format, memory-safety, fuzzing, vfxfonts, graphics-stack, variable-fonts, webfonts
Last editorial update10h ago5d ago
WebsiteVisit →Visit →

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.

Read the full OpenEXR trajectory →

What is systemfonts?

The R font layer stopped matching fonts and started acquiring them.

systemfonts is the font matching and shaping engine underneath ragg, svglite and textshaping, and its recent releases have pushed it well past its original job. It can now register uninstalled font files, pull fonts from Google Fonts and Bunny Fonts, emit stylesheet imports for HTML and SVG embedding, and hand glyph outlines and bitmaps to other C-level consumers. The last two releases are pure upkeep: a FreeType compilation fix, a sanitizer issue, and a workaround for a broken macOS system font.

Read the full systemfonts trajectory →

OpenEXR vs systemfonts: editorial side-by-side

O
OpenEXR
DESIGN
5.0

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.

S0.0

The R font layer stopped matching fonts and started acquiring them.

◆ Current state

systemfonts is the font matching and shaping engine underneath ragg, svglite and textshaping, and its recent releases have pushed it well past its original job. It can now register uninstalled font files, pull fonts from Google Fonts and Bunny Fonts, emit stylesheet imports for HTML and SVG embedding, and hand glyph outlines and bitmaps to other C-level consumers. The last two releases are pure upkeep: a FreeType compilation fix, a sanitizer issue, and a workaround for a broken macOS system font.

◆ Where it's heading

The arc is from passive lookup to active font provisioning. Variable font support in 1.3.0 is the clearest marker — it is explicitly gated on downstream packages upgrading to use it, which means systemfonts is now setting the pace for the rest of the R graphics stack rather than following it. Reference counting on cached faces points the same direction: the package is being hardened as a shared resource other packages hold handles into, not a leaf utility.

◆ Prediction

Expect the deprecation of the bold argument in favour of weight to complete, and expect the variable-font API to show up in ragg and svglite before it shows up in user-facing packages.

Alternatives to OpenEXR and systemfonts

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 OpenEXR or systemfonts.

See all OpenEXR alternatives → · See all systemfonts alternatives →

Recent activity from OpenEXR and systemfonts

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 11h agoOpenEXR3.3.14 backports the IDManifest memory fixes to the 3.3 stream
  2. 12h agoOpenEXR3.4.15 fixes two IDManifest memory-allocation flaws
  3. 14d agoOpenEXR3.4.14 fixes 15 CVEs found by fuzzing the .exr parser
  4. 14d agoOpenEXR3.3.13 backports the same 15 CVE fixes to the 3.3 stream
  5. 14d agoOpenEXR3.2.11 carries 10 of the CVE fixes to the oldest supported stream
  6. 2mo agoOpenEXR3.3.12-rc updates CI install scripts
  7. 5mo agosystemfontsCompile fixes for old FreeType and a broken macOS font
  8. 10mo agosystemfontsSanitizer fix in variation axis name conversion
  9. 10mo agosystemfontsVariable font support lands across systemfonts
  10. 1y agosystemfontsFont embedding stylesheets and C-level glyph access
  11. 1y agosystemfontsadd_fonts() accepts URLs; macOS compile fix
  12. 1y agosystemfontsMemory and download fixes in the new font-fetching path

Frequently asked questions

What is the difference between OpenEXR and systemfonts?

They serve adjacent needs but don't currently overlap on shipped themes. 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 OpenEXR better than systemfonts?

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 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.

What are the best alternatives to systemfonts?

Top systemfonts alternatives in Design are ranked by recent ship velocity. Browse the "systemfonts alternatives" section above for the current picks, or visit /alternatives/systemfonts for the full list with editorial commentary on each.