Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of ZoneMinder and CRI-O — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Patch tags land monthly with release notes that itemize nothing.
The three most recent CRI-O entries are v1.34.11, v1.34.10 and v1.33.13, cut roughly a month apart across two supported minor lines. All three carry auto-generated notes whose 'Changes by Kind' sections are empty or labelled Uncategorized, with the body given over to download bundles, checksums, SPDX manifests and signatures. Only v1.34.10 admits to a Bug or Regression category, and does not say what it was.
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.
The three most recent CRI-O entries are v1.34.11, v1.34.10 and v1.33.13, cut roughly a month apart across two supported minor lines. All three carry auto-generated notes whose 'Changes by Kind' sections are empty or labelled Uncategorized, with the body given over to download bundles, checksums, SPDX manifests and signatures. Only v1.34.10 admits to a Bug or Regression category, and does not say what it was.
What the feed does show is release engineering: every tag ships static bundles per architecture with checksums, SPDX SBOMs and signing bundles, which is the supply-chain posture Kubernetes runtimes are now expected to hold. The absence of itemized changes means the actual runtime work is invisible here, so read this feed as a release calendar for the 1.33 and 1.34 branches rather than a changelog.
Expect the same monthly patch cadence on both maintained branches, with content that stays uncategorized unless the project changes how it generates notes.
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 ZoneMinder or CRI-O.
The public feed carries tags and image manifests; the release notes live in Prime docs.
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.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
See all ZoneMinder alternatives → · See all CRI-O alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CRI-O is currently shipping more aggressively (velocity 2.5 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. CRI-O is currently shipping more aggressively (velocity 2.5 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 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.
Top CRI-O alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CRI-O alternatives" section above for the current picks, or visit /alternatives/cri-o for the full list with editorial commentary on each.