https://privsec.dev/posts/android/f-droid-security-issues/
https://www.privacyguides.org/en/android/obtaining-apps/#f-d...
My understanding is that this largely stems from the fact that F-Droid compiles and signs all the apps on behalf of the application developers, so there is a loss of control there. Some will say that this is what redistributable builds are for, but in my experience they are not actively/widely verified even if they do support it, especially publicly.
Practically speaking, you should just assess the following threat model; which is going to be a greater threat to you:
* An application developer who can be bought out and have their tools replaced with adware. (Ref. https://news.ycombinator.com/item?id=38505229 )
* The F-Droid servers, where the most realistic threat is a rogue actor obtaining the keys.
That second one is also mitigated by the fact that F-Droid generally prefers to practice "reproducible signing"; basically they'll distribute the developers apk, not the one on F-Droids buildserver, if the F-Droid release matches the GitHub release (minus the signature obviously), making the signature problem mostly a non-issue.
For most people, I'd argue the former (a "surprise update" to insert anti-features[0]) is a greater risk than the latter, so F-Droids model fits them better. The sole exception would be extremely privacy sensitive apps where trusting the developer is more paramount than having the second man in-the-middle that F-Droids maintainers are. (A basic example of that would probably be Signal.)
[0]: As defined here, although not all are relevant for users: https://f-droid.org/docs/Anti-Features/ , although I'd just add de facto adding pointless microtransactions and subscriptions to this list. They're just not included since F-Droid wouldn't ship them.
This happens at an alarming rate within the video game emulation community. Many projects (including MAME) have openly expressed deep disdain for any forks existing at all. It's like they think any difference a fork has is a negative thing and then aggressively attack that... as if there is only one way to write software. Some projects have even stopped upstream development entirely, or closed the source or changed their license... just over forks. License violations (including GPL as well as non-commercial ones) are also rampant there.
At least they are open and honest about it. As opposite to Google, who promised to let developers do the signing, but soon (after gaining worldwide popularity) took over with extremely shoddy justification.
I trust F-Droid more than $RANDOM_GITHUB_ACCOUNT.
IMHO, one of the best parts about the F-Droid ecosystem is its openness. Security models are not a one-size-fits-all and it is important to me to have access to software from multiple sources.
Some projects don't even provide an F-Droid release, so just adding the github repository to Obtainium is much easier than having to deal with apk stuff.
There is no good alternative to F-Droid. Thankfully that's just because it is such a great concept.
https://forum.f-droid.org/t/known-repositories/721
Izzyondroid is the only one I've added in the past.
It's particularly good for very niche use cases, like, you might need an app that simulates dice rolls, then fdroid might be the best place for that as you'll find an app that does just that and nothing else. No ads, no bullshit.
If fdroid doesn't work for me then I will give in and search for "commercial" (ads or paid) solutions.