/e/OS is not fully degoogled, as DNS connectivity checks, hardware attestation provisioning, and eSIM activation all go through Google.
It is often many weeks or months behind on security updates, especially in the WebView, which makes it easy to exploit.
It doesn't support bootloader locking on many devices, and if you lock the bootloader on a phone that does support it, it could brick if /e/OS is on an older security patch than the stock ROM was.
It doesn't use a lot of the hardening in GrapheneOS such as hardened_malloc which prevents memory corruption exploits, even if the hardware supports it.
And finally, /e/OS's text-to-speech sends what you say to OpenAI, despite local options being available.
If you want a properly secure Android phone, the best option is GrapheneOS, however it only supports Pixel phones and future Motarola phones due to its high security requirements.
If you can't get a Pixel then iOS in lockdown mode is the next best option, however if you can't replace your phone, LineageOS is much worse than Graphene although it is still much better than /e/.
the fun thing is like, I use grapheneOS on a pixel 10 pro, though I find it kind of difficult to fess up to given the cringeworthy escapades of the graphene community.
who pissed in their cereal? does the mere presence of other ROM projects attack their identity in some way? have they claimed to be more secure than GOS and others?
You're an ungrateful one huh. I wonder if you hate any of the other people who make software you use. 🤔💭
Wow what a leap. note that i said community and not project members, though they've not been without controversy either. let's not pretend micay wasn't massively problematic,