werf
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
A side-by-side editorial comparison of YARA and ZoneMinder — release velocity, themes, recent moves, and the top alternatives to consider.
YARA ships bounds checks, not features — three patch releases published thirteen minutes apart.
Every release in this window is memory safety work on the parsers. The July batch bounds the rule table index in two opcodes, the tilde stream row count in the dotnet module and the repeat stack depth in the regex fiber sync, and fixes a leak in rule stream loading. Earlier releases closed a heap overflow triggered by hand-crafted compiled rules, infinite loops on corrupt PE resource directories, and an integer overflow in ELF parsing. The three most recent tags were published within thirteen minutes of each other.
ZoneMinder 1.38 finally split capturing from analysing — and added roles to a system that had none.
ZoneMinder runs two lines in parallel. The 1.38 series, opened in February, brought role-based access control, WebRTC, Go2RTC and RTSP2Web streaming with hardware acceleration, a redesigned monitor model splitting Capturing, Analysing and Recording into separate settings, ONVIF events, MQTT and event tagging. The legacy 1.36 branch is still receiving fixes, including a stored SQL injection through event name and cause fields. The 1.38.1 release replaced four vendor-specific ONVIF implementations with a single control module.
Every release in this window is memory safety work on the parsers. The July batch bounds the rule table index in two opcodes, the tilde stream row count in the dotnet module and the repeat stack depth in the regex fiber sync, and fixes a leak in rule stream loading. Earlier releases closed a heap overflow triggered by hand-crafted compiled rules, infinite loops on corrupt PE resource directories, and an integer overflow in ELF parsing. The three most recent tags were published within thirteen minutes of each other.
YARA is being maintained as an input parser under adversarial pressure rather than developed as a language. The last release to add anything — 4.5.0, with unreferenced string rules, strict escape warnings and a slow-rule callback — is nearly two years back, and everything since has been bounding a value someone found a way to overflow. Even the scan limit change was a revert to a prior default.
Expect the pattern to hold: batched patch releases whose contents are bounds checks in the PE, dotnet and regex paths, since that is where every recent finding has landed. Nothing in these entries suggests new language or module capability is queued.
ZoneMinder runs two lines in parallel. The 1.38 series, opened in February, brought role-based access control, WebRTC, Go2RTC and RTSP2Web streaming with hardware acceleration, a redesigned monitor model splitting Capturing, Analysing and Recording into separate settings, ONVIF events, MQTT and event tagging. The legacy 1.36 branch is still receiving fixes, including a stored SQL injection through event name and cause fields. The 1.38.1 release replaced four vendor-specific ONVIF implementations with a single control module.
The project is consolidating a decade of accumulated special cases: four ONVIF implementations become one, monitor function modes become independent toggles, and streaming moves onto standard components rather than bespoke paths. Meanwhile 1.36 keeps being patched for security and build compatibility, which means a substantial install base has not moved. Release engineering itself is visibly strained — 1.38.2 was abandoned mid-flight over a Debian packaging conflict.
Expect 1.38 patch releases to keep folding in security and memory-safety fixes while the 1.36 branch receives only vulnerability backports until it is retired. Whether the new streaming stack becomes the default rather than an option is not settled by these entries.
Other Infra & APIs 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 YARA or ZoneMinder.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
Patch tags land monthly with release notes that itemize nothing.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
See all YARA alternatives → · See all ZoneMinder alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. YARA 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. YARA 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 Infra & APIs products to evaluate alongside.
Top YARA alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "YARA alternatives" section above for the current picks, or visit /alternatives/yara for the full list with editorial commentary on each.
Top ZoneMinder alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ZoneMinder alternatives" section above for the current picks, or visit /alternatives/zoneminder for the full list with editorial commentary on each.