← Back to home
Comparison · Collab

CommaFeed vs File Browser

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

Shared themes:self-hostedsecurity-hardening

CommaFeed vs File Browser: at a glance

FeatureCommaFeedFile Browser
SectorCollabCollab
Velocity score5.06.3
Sparks · 30d01
Top themesrss-reader, self-hosted, security-hardening, ssrfend-of-life, self-hosted, file-manager, security-hardening
Last editorial update1h ago16d 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 File Browser?

File Browser is shutting down — the repo archives on 2026-09-01 and no security fixes follow.

The project spent July shipping a rapid series of hardening releases — path canonicalization before access checks, atomic user provisioning, TUS upload length enforcement, download-permission gates, case-folded home directory collisions, several GHSA-tracked share and auth advisories — and then announced it was winding down. 2.63.23 is the last planned release; the repository archives on 2026-09-01.

Read the full File Browser trajectory →

CommaFeed vs File Browser: 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.

F6.3

File Browser is shutting down — the repo archives on 2026-09-01 and no security fixes follow.

◆ Current state

The project spent July shipping a rapid series of hardening releases — path canonicalization before access checks, atomic user provisioning, TUS upload length enforcement, download-permission gates, case-folded home directory collisions, several GHSA-tracked share and auth advisories — and then announced it was winding down. 2.63.23 is the last planned release; the repository archives on 2026-09-01.

◆ Where it's heading

The shape of the final weeks tells the story: almost every commit was a scope-escape or permission-bypass fix, which is a heavy load for a Go binary that many people expose directly to the internet. Rather than keep absorbing that, the maintainers are stopping. Existing releases and Docker images stay online, but from September there is no one fixing the next advisory.

◆ Prediction

Existing deployments keep working and keep accumulating unpatched vulnerabilities; expect the community to consolidate around a fork or one of the existing alternatives before the archive date.

Alternatives to CommaFeed and File Browser

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 File Browser.

See all CommaFeed alternatives → · See all File Browser alternatives →

Recent activity from CommaFeed and File Browser

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

  1. 1d agoCommaFeedHost header injection closed on the password recovery endpoint
  2. 8d agoCommaFeedGoogle Reader API support and secure-by-default local address blocking
  3. 16d agoCommaFeedjavascript: URLs now filtered at parse time, not just in the client
  4. 22d agoFile BrowserFinal release: project winds down, repo archives 2026-09-01
  5. 22d agoFile BrowserWind-down notice lands with recursive-rule and proxy-token fixes
  6. 24d agoFile BrowserPaths canonicalized before access rules are checked
  7. 24d agoFile BrowserProvisioned scope check made atomic with the save
  8. 25d agoFile BrowserTUS upload limits, checksum permission gate, scope isolation
  9. 1mo agoCommaFeedFeed-declared icons, starred-entry search, and image-proxy SSRF limits
  10. 1mo agoFile BrowserCopy/move conflict checks and EPUB preview fix
  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 File Browser?

Both compete on the same themes — self-hosted, security-hardening — within Collab. File Browser 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.

Is CommaFeed better than File Browser?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. File Browser 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.

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 File Browser?

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