Ethico
The whistleblower hotline vendor is assembling a compliance suite, one module at a time.
A side-by-side editorial comparison of File Browser and FreshRSS — release velocity, themes, recent moves, and the top alternatives to consider.
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.
FreshRSS keeps turning a reader into a queryable archive — and hardening the parts that touch the web.
Two major releases and their bug-fix follow-ups define this window. 1.28.0 added sorting and filtering by user-modified date with a matching search operator, sorting by article length, an advanced search form, an overview of dates with the most unread articles, and API-level sharing of feed visibility. 1.29.0 layered on sort-order preferences at global, category and feed level, feed-provided icons, and a purge CLI. Security work runs alongside throughout — cURL restricted to HTTP and HTTPS, reauthentication in sudo mode, Content-Security-Policy frame-ancestors, and compliance with HTTP 429 and 503 including Retry-After.
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.
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.
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.
Two major releases and their bug-fix follow-ups define this window. 1.28.0 added sorting and filtering by user-modified date with a matching search operator, sorting by article length, an advanced search form, an overview of dates with the most unread articles, and API-level sharing of feed visibility. 1.29.0 layered on sort-order preferences at global, category and feed level, feed-provided icons, and a purge CLI. Security work runs alongside throughout — cURL restricted to HTTP and HTTPS, reauthentication in sudo mode, Content-Security-Policy frame-ancestors, and compliance with HTTP 429 and 503 including Retry-After.
The feature line is consistently about retrieval rather than reading: search operators, sort dimensions, date overviews and per-level preferences all treat the archive as a queryable dataset instead of an inbox to clear. In parallel, the CLI surface keeps growing — purge policies, SQLite export with retention — which points at self-hosters automating maintenance rather than clicking through settings. Security fixes are steady and specific to the fact that a feed reader fetches arbitrary remote content, which is what makes the cURL protocol restriction and CSP work necessary rather than optional. Releases pair a feature drop with a fast bug-fix follow-up every time.
Given the pattern of a major release followed within weeks by a patch, and the steady expansion of CLI commands, expect the next major to continue extending search and automation surfaces rather than reworking the reading experience.
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 File Browser or FreshRSS.
The whistleblower hotline vendor is assembling a compliance suite, one module at a time.
Contract automation grows up: admin permission maps, 2FA, and forms that do their own arithmetic.
The knowledge graph quietly turned itself into a meetings product.
A minimal RSS reader that made passkeys the only way in, then went back to polishing the reading experience.
A Go bookmark manager rebuilding itself around an API — and only ever shipping release candidates.
A self-hosted reading server that spent two releases becoming infrastructure, then paid for it with a CVE.
See all File Browser alternatives → · See all FreshRSS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Collab. File Browser is currently shipping more aggressively (velocity 6.3 vs 0.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. File Browser is currently shipping more aggressively (velocity 6.3 vs 0.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 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.
Top FreshRSS alternatives in Collab are ranked by recent ship velocity. Browse the "FreshRSS alternatives" section above for the current picks, or visit /alternatives/freshrss for the full list with editorial commentary on each.