Overview: Support thread for Unraid progressive web app (Unraid-PWA).

Application: https://github.com/laurensguijt/Unraid-PWA

Container Image: ghcr.io/laurensguijt/unraid-pwa:latest

GitHub Discussion: https://github.com/laurensguijt/Unraid-PWA/discussions

Very cool, i presume that it will make it to the CA apps

Not meant to be nasty by asking, but this gives the strong impression of being vibe coded.
For a web interface that isn't really a bad thing, but I'd like to know if it is. The entry in the Community Apps is also barren with little description, no issues and no community discussions. So I hope you can understand the questions.

Edited February 27Feb 27 by skywalker6705

On 2/26/2026 at 9:36 PM, skywalker6705 said:

Not meant to be nasty by asking, but this gives the strong impression of being vibe coded.
For a web interface that isn't really a bad thing, but I'd like to know if it is. The entry in the Community Apps is also barren with little description, no issues and no community discussions. So I hope you can understand the questions.

Their reddit post was a little more informative:

And yes, parts of this project were developed with AI assistance. I see it as a starting point and a solid foundation for the community to build on and improve over time.

Which then devolved into arguing. Someone else used ChatGippity to find a non-trivial risk of API key leakage which went unremarked on, so who knows if that is real or has been fixed:

I had ChatGPT review the code. There were a few minor things but this seems like a real potential issue you should address:

API key leak via external icon URLs: if any Docker container has net.unraid.docker.icon set to an external https://…, the backend may fetch it and (currently) include the Unraid x-api-key header. You should patch the backend to only attach x-api-key when fetching from your Unraid baseUrl origin (or skip external icons entirely).