yay has +2560 and paru has +1181, both of these are popular enough to be considered adopted as extra.
Both have `-bin` version of precompiled packages, which I'd assume many would resort to if build fails for them. > You should not use the AUR if you don't know that "building a package" > entails and what parts an > AUR helper automates and what parts it does not. Call it the "entrance > exam" :) If the goal here is to protect the user, wouldn't it make sense to have vetted AUR helper that follows certain criteria, such as showing PKGBUILD, tell them about how these are community maintained? Imagine if there were a "very-helpful" AUR helper that promises auto update, zero user interaction, completely shielding users from the build process. Vetting known-good helpers would prevent those helpers from getting main stream, while funneling users to understand the build system. I think the goal should be helping user while keeping them safe, rather than letting them figure out things on their own and potentially seeking the easy (wrong) way out.
