SiYuan
SiYuan stabilises 3.8.1 after a seven-build beta run, all of it widening the agent surface it opened in 3.8.0
A side-by-side editorial comparison of CommaFeed and Kavita — release velocity, themes, recent moves, and the top alternatives to consider.
CommaFeed is patching its way through the attack surface a self-hosted reader inherits
CommaFeed's 7.x line has become a sustained security pass. The newest patch closes Host header injection on the password recovery endpoint and adds a commafeed.password-recovery-public-base-url setting so the email base URL is configured rather than taken from the request. Behind it: local address blocking made secure by default alongside Google Reader API support in 7.3.0, javascript: URLs filtered at parse time in 7.2.1, and SSRF limits on the image proxy in 7.2.0.
A self-hosted reading server that spent two releases becoming infrastructure, then paid for it with a CVE.
Kavita ships two to four substantial releases a year with hotfixes trailing each one, and the last two years moved it well past a comic reader: OIDC login, an annotation system, a rebuilt epub reader, a reading-list overhaul, a stats system, and a scanner reported 50x faster. The most recent release is a critical security hotfix carrying CVE-2026-47202 that affects every prior version. Kavita+ remains the paid tier where metadata features land first.
CommaFeed's 7.x line has become a sustained security pass. The newest patch closes Host header injection on the password recovery endpoint and adds a commafeed.password-recovery-public-base-url setting so the email base URL is configured rather than taken from the request. Behind it: local address blocking made secure by default alongside Google Reader API support in 7.3.0, javascript: URLs filtered at parse time in 7.2.1, and SSRF limits on the image proxy in 7.2.0.
Every release in this stretch closes a path where content or a request from outside the instance was trusted too far - feed URLs reaching internal addresses, proxied images, javascript: links, and now a header shaping an outbound email. That is the checklist of a project being run as a multi-user hosted service rather than a single-user tool, and it follows directly from the 7.0.0 decision to sandbox filter expressions. Feature work continues in parallel but is clearly the smaller half.
The remaining untrusted-input surfaces - OPML import and the feed fetcher's redirect handling - are the likely next targets. The pattern of shipping each fix as its own patch release should continue rather than batching them.
Kavita ships two to four substantial releases a year with hotfixes trailing each one, and the last two years moved it well past a comic reader: OIDC login, an annotation system, a rebuilt epub reader, a reading-list overhaul, a stats system, and a scanner reported 50x faster. The most recent release is a critical security hotfix carrying CVE-2026-47202 that affects every prior version. Kavita+ remains the paid tier where metadata features land first.
The arc is a hobby-scale project taking on the obligations of infrastructure — standard auth, an external API contract for third-party clients, sync with other readers, and formal vulnerability disclosure. Each of those decisions expands the attack surface, and the 0.9.x line shows the bill arriving: security hardening now leads the release notes rather than following them. The team has also visibly grown from one maintainer to a named pair, which is what made the parallel reader and foundation rewrites possible.
The next release is likely the delayed scanner-improvement work that 0.8.7 displaced, with continued API hardening rather than new reader surfaces. Expect the CVE details to be published once adoption of 0.9.0.2 is high enough.
Other Collab 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 CommaFeed or Kavita.
SiYuan stabilises 3.8.1 after a seven-build beta run, all of it widening the agent surface it opened in 3.8.0
Hive ships in batches, and this one is all planning accuracy and admin control.
Teable ships daily, and the work has moved from grid features to platform governance.
Simpplr publishes the research that names the gap, then ships the product that closes it.
NetNewsWire's 7.1.3 train has moved from rebuilding sync to sweeping up what the rebuild disturbed.
Document360 rebuilt its API for agents; now it's turning the AI inward on authoring.
See all CommaFeed alternatives → · See all Kavita alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted, security-hardening — within Collab. CommaFeed 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. CommaFeed 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 Collab products to evaluate alongside.
Top CommaFeed alternatives in Collab are ranked by recent ship velocity. Browse the "CommaFeed alternatives" section above for the current picks, or visit /alternatives/commafeed for the full list with editorial commentary on each.
Top Kavita alternatives in Collab are ranked by recent ship velocity. Browse the "Kavita alternatives" section above for the current picks, or visit /alternatives/kavita for the full list with editorial commentary on each.