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 Paperless-ngx — 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.
Paperless-ngx shipped its 3.0 rewrite, then spent a week putting out the fires.
3.0.0 landed on July 22 after a long beta, carrying both the largest feature set in the project's history and nine breaking changes. The five releases since are pure repair: a broken migration in 3.0.1 that forced an immediate 3.0.2, then three patch rounds covering OCR skipping, permission-filtered dedup, Gotenberg conversion, email date parsing, AI suggestion caching and search index edge cases. The pace tells you 3.0 shipped into real deployments fast.
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.
3.0.0 landed on July 22 after a long beta, carrying both the largest feature set in the project's history and nine breaking changes. The five releases since are pure repair: a broken migration in 3.0.1 that forced an immediate 3.0.2, then three patch rounds covering OCR skipping, permission-filtered dedup, Gotenberg conversion, email date parsing, AI suggestion caching and search index edge cases. The pace tells you 3.0 shipped into real deployments fast.
The project has moved from a document scanner-and-tagger to a document platform with AI in the core: Paperless AI, remote OCR via Azure, a document parser plugin framework, tantivy replacing Whoosh for search, file versions and sharelink bundles. The breaking changes are the other half of that story — dropping API v1, Python 3.10, document encryption and the old consumer clears the decks for that platform. Recent patches keep touching LLM plumbing, including passing output language into chat and adding docstrings so the classifier reads better as an LLM tool.
The 3.0.x patch cadence looks set to run at least another round or two — 3.0.5 is still landing search-compatibility and AI-suggestion fixes rather than tapering. Feature work resuming before that queue empties would be the surprise.
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 Paperless-ngx.
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 Paperless-ngx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Collab. Paperless-ngx is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. Paperless-ngx is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Paperless-ngx alternatives in Collab are ranked by recent ship velocity. Browse the "Paperless-ngx alternatives" section above for the current picks, or visit /alternatives/paperless-ngx for the full list with editorial commentary on each.