Once I would have used this, but I can't just can't bring myself to trust forks by small or unknown teams. We trust browsers with passwords to everything in our lives, like our bank details. The FAQ doesn't even cover who created LibreWolf. Why should I trust them? Even if I do trust the developers, are they really capable of keeping a modern complex browser secure in the hostile environment of todays internet? It ha…
- automatic builds and uploads via GitHub/GitLab CI (or similar) from a well-commented build script
- all the knobs for reproducible builds set up, so anyone can fork the repo, run the CI themselves, and see that it's bit-for-bit the same thing
- an automatic merge or rebase of the latest stable release tag, and the result of that merge being plugged into automatic updates
- an automatic merge or rebase of the latest beta tag (or even nightly), and some form of alerting if the build fails
- perhaps some Selenium + Wireshark automation to see what requests happen and make sure there are no unexpected ones
And, actually, it seems like LibreWolf is on the way there. https://gitlab.com/librewolf-community/browser/common has a decently-well-commented build script that grabs the latest tarball from Mozilla and builds on top of it and even supports building on nightly, and their documentation (https://librewolf-community.gitlab.io/docs/) mentions that as well. But I don't see where it is run / who runs it, and what they do if the build fails.
(Honestly it seems like setting up the release automation and alerting is a substantial project in itself.)