Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of ClamAV and CRI-O — release velocity, themes, recent moves, and the top alternatives to consider.
ClamAV's file parsers keep yielding CVEs — and every fix ships twice, to two branches.
ClamAV runs two supported lines, 1.5.x and 1.4.x, and publishes identical patch releases seconds apart whenever a vulnerability lands. The recurring source is the same: file format parsers. The July pair fixed a PESpin unpacker use-after-free and an integer overflow in PE rebuild size calculations; the March pair fixed an HTML parser error-handling crash and a JPEG scanning hang inherited from a Rust image dependency. One of the July issues reaches back to code from 2005.
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.
ClamAV runs two supported lines, 1.5.x and 1.4.x, and publishes identical patch releases seconds apart whenever a vulnerability lands. The recurring source is the same: file format parsers. The July pair fixed a PESpin unpacker use-after-free and an integer overflow in PE rebuild size calculations; the March pair fixed an HTML parser error-handling crash and a JPEG scanning hang inherited from a Rust image dependency. One of the July issues reaches back to code from 2005.
Feature work has effectively paused since 1.5.0 last October, which added OLE2 encryption detection and HTML URI recording in JSON metadata. Everything since is patch traffic. The more consequential trend is the Rust dependency chain: fixing image parsing bugs by upgrading crates has twice forced the minimum Rust compiler version upward, which pushes cost onto distribution packagers rather than end users.
Expect the dual-branch CVE pattern to continue at roughly quarterly intervals, with the PE and archive parsers the likeliest source given their history here. Whether a 1.6 line opens is not something these entries indicate — there has been no development release since the 1.5.0 cycle.
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 ClamAV 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 ClamAV 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 ClamAV alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ClamAV alternatives" section above for the current picks, or visit /alternatives/clamav 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.