← Back to home
Comparison · Collab

CommaFeed vs EGroupware

A side-by-side editorial comparison of CommaFeed and EGroupware — release velocity, themes, recent moves, and the top alternatives to consider.

CommaFeed vs EGroupware: at a glance

FeatureCommaFeedEGroupware
SectorCollabCollab
Velocity score5.05.0
Sparks · 30d00
Top themesrss-reader, self-hosted, security-hardening, ssrfsecurity, self-hosting, groupware, end-of-life
Last editorial update2h ago7d ago
WebsiteVisit →Visit →

What is CommaFeed?

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.

Read the full CommaFeed trajectory →

What is EGroupware?

EGroupware's feed has become a security treadmill, with the 23.1 branch days from end of life.

Almost every release in this window is a security release, and most ship as a pair — one build for 26.x, an identical-scope backport for 23.1. Feature work exists but arrives as single lines inside those security notes: WebAuthN two-factor moving out of the former EPL add-on, OpenID bumped to current upstream libraries, invoice XML gaining reverse-charge exemption codes. The recurring theme in the fixes themselves is authentication — OAuth bearer tokens, OpenID regressions, an inverted email_verified check, passkeys broken by a missing proxy config.

Read the full EGroupware trajectory →

CommaFeed vs EGroupware: editorial side-by-side

C
CommaFeed
COLLAB
5.0

CommaFeed is patching its way through the attack surface a self-hosted reader inherits

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

E5.0

EGroupware's feed has become a security treadmill, with the 23.1 branch days from end of life.

◆ Current state

Almost every release in this window is a security release, and most ship as a pair — one build for 26.x, an identical-scope backport for 23.1. Feature work exists but arrives as single lines inside those security notes: WebAuthN two-factor moving out of the former EPL add-on, OpenID bumped to current upstream libraries, invoice XML gaining reverse-charge exemption codes. The recurring theme in the fixes themselves is authentication — OAuth bearer tokens, OpenID regressions, an inverted email_verified check, passkeys broken by a missing proxy config.

◆ Where it's heading

The project is consolidating everyone onto 26.x and has put a date on it: security coverage for 23.1 ends August 15, 2026, repeated as a warning in every 23.1 build since July. After that the twin-release pattern should stop and the cadence should halve. The authentication stack is the least settled part of the codebase right now — the July and August releases keep re-fixing OpenID and WebAuthN regressions introduced by their own predecessors.

◆ Prediction

Expect 23.1 builds to cease after August 15 and the feed to become single-track 26.x. On the evidence of the last six releases, expect at least one more OpenID or WebAuthN regression fix to follow the recent upstream library bump.

Alternatives to CommaFeed and EGroupware

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 EGroupware.

See all CommaFeed alternatives → · See all EGroupware alternatives →

Recent activity from CommaFeed and EGroupware

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoCommaFeedHost header injection closed on the password recovery endpoint
  2. 7d agoEGroupwareSecurity release fixes passkey regression and OAuth token errors
  3. 8d agoCommaFeedGoogle Reader API support and secure-by-default local address blocking
  4. 14d agoEGroupware23.1 security release; branch support ends August 15
  5. 14d agoEGroupwareWebAuthN two-factor moves into core, plus security fixes
  6. 16d agoCommaFeedjavascript: URLs now filtered at parse time, not just in the client
  7. 26d agoEGroupwareSecurity release repairs merge-print and ImportExport regressions
  8. 26d agoEGroupware23.1 security backport with end-of-support warning
  9. 1mo agoEGroupwareTwo more security fixes for the 23.1 branch
  10. 1mo agoCommaFeedFeed-declared icons, starred-entry search, and image-proxy SSRF limits
  11. 4mo agoCommaFeedMobile unread count in the header plus a graceful refresh shutdown
  12. 5mo agoCommaFeedFilter expressions move from JEXL to a sandboxed visual query builder

Frequently asked questions

What is the difference between CommaFeed and EGroupware?

They serve adjacent needs but don't currently overlap on shipped themes. CommaFeed and EGroupware are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is CommaFeed better than EGroupware?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. CommaFeed and EGroupware are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.

What are the best alternatives to CommaFeed?

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.

What are the best alternatives to EGroupware?

Top EGroupware alternatives in Collab are ranked by recent ship velocity. Browse the "EGroupware alternatives" section above for the current picks, or visit /alternatives/egroupware for the full list with editorial commentary on each.