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 Shiori — 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.
A Go bookmark manager rebuilding itself around an API — and only ever shipping release candidates.
Shiori is a self-hosted read-later and bookmark tool whose recent history is entirely release candidates: v1.7.0-rc.2, rc.3, v1.7.2-rc.1, v1.8.0-rc.1. The visible work has moved off the web UI and into an API v1 surface — tag endpoints, bookmark-tag association, filtering and counts — plus infrastructure like proxy-header authentication and SQLite performance. The last tagged release in this window is from July 2025.
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.
Shiori is a self-hosted read-later and bookmark tool whose recent history is entirely release candidates: v1.7.0-rc.2, rc.3, v1.7.2-rc.1, v1.8.0-rc.1. The visible work has moved off the web UI and into an API v1 surface — tag endpoints, bookmark-tag association, filtering and counts — plus infrastructure like proxy-header authentication and SQLite performance. The last tagged release in this window is from July 2025.
The project is converting from a web app with an API bolted on into an API-first service with a client, and the login component, PWA and theme work are being rewritten around that split. Proxy forward-header authentication in particular is a deployment-shape decision: it assumes Shiori sits behind an authenticating reverse proxy rather than owning identity itself. The RC-only tagging pattern makes it hard to tell what the maintainers consider stable.
The next step is presumably a final v1.8.0 consolidating the API v1 tag work, though nothing in these entries indicates the RC-to-stable promotion is scheduled. If the pattern holds, the following RC continues on API endpoints rather than the UI.
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 Shiori.
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 self-hosted reading server that spent two releases becoming infrastructure, then paid for it with a CVE.
FreshRSS keeps turning a reader into a queryable archive — and hardening the parts that touch the web.
See all File Browser alternatives → · See all Shiori 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 Shiori alternatives in Collab are ranked by recent ship velocity. Browse the "Shiori alternatives" section above for the current picks, or visit /alternatives/shiori for the full list with editorial commentary on each.