Project Abandoned??

[bscott]

Is it safe to say that, since there's been no merging of pull requests, tons of unanswered issues and pull requests that haven't been reviewed emerged, and this project is fully abandoned since there hasn't been a release in about two years? Are there any active forks of this? Can we please archive this repo if it's not truly being maintained..

[54ty1BkRU5zyEvsQ]

i wish they would open up ownership of the project so the community can take over if ice whale is abandoning it

[inkly]

Are there any active forks of this?

Yes.

I publish one at github.com/ReCasaOS. It continues alvins82's fork, whose releases are what kept CasaOS installable on Docker 29 and Ubuntu 26; mine start at v0.4.40 where his ended at v0.4.39 on 20 August 2026, and his notes are kept in my README. If you want the smaller delta from upstream, look at his first.

curl -fsSL https://github.com/ReCasaOS/CasaOS-Install/releases/latest/download/install.sh | sudo bash

It is not "the same code kept building". The core alone is 102 commits and about 3,900 added lines ahead of main here, with two-factor authentication, a Vue 3 dashboard with a dark theme, a Compose editor and per-app .env files on top. An upgrade is in place and has no rollback; it does not touch /DATA, and there is an uninstaller.

What it honestly is, so nobody installs it on a wrong impression:

• It is six days old as a public distribution. First release 4 September 2026, 26 releases to date. Every one is installed on my own box before publishing — that box is essentially the whole test population. Two of those releases shipped regressions I then had to fix: the Vue 3 move broke four things in the dashboard, and a fix for a greyed-out app card put casaos-app-management into a crash loop and the dashboard into 502s. Both were fixed the same day, which is the good half of that sentence and not the whole of it.
• Cloud-drive mounts do not work here, and IceWhale's release is where they still do. Google Drive, OneDrive and Dropbox ship with client_id at its default, "private build", so sign-in cannot complete. IceWhale's release workflow injected real OAuth credentials; the fork lineage this builds on replaced that workflow with a plain go build in August 2026, and the flags meant to inject them have been inert since. Fixing it needs OAuth applications registered in this project's own name, which I have not done. If cloud mounts are why you run CasaOS, this changes nothing for you.
• It is not affiliated with IceWhale and claims no endorsement. CASAOS is their trademark; the name says what this is a distribution of, nothing more. Their per-file copyright notices are kept, and the installer credits this repository as upstream.
• The App Store is still theirs. The catalogue is still IceWhale's, still polled live, still curated by them. Nothing about the store changed, and if that stops, a fork does not fix it.
• It does not answer the comment above. Nobody has opened up ownership of this project. This is one person publishing builds, which is a different thing from community stewardship.

For the question in the title, the numbers as of today: last stable release v0.4.15 (19 December 2024), last pre-release v0.4.17-alpha1 (17 April 2025), last commit to main 6 August 2025, 820 open issues and 13 open pull requests. The repository is not archived.