What we don't trust are user repositories, where anons like you and me can publish a binary.
Great point supporting the wrong argument. AUR does NOT host binaries - there is NO WAY for anon to make a binary available directly to Arch users. Let's all get this clear.
What is the AUR?
The AUR (Arch User Repository) is a community-driven repository of build scripts called PKGBUILDs. It doesn't host packages themselves — it hosts recipes that tell your system how to fetch sources and compile/package software locally.
What it hosts: PKGBUILDs for software not in the official repos — proprietary apps (Spotify, Chrome), bleeding-edge or -git versions, niche tools, and packages awaiting promotion to official repos. The scripts are user-submitted and unvetted, so you should read a PKGBUILD before building.
What's a PKGBUILD?
Typical basic example:
# Maintainer: Your Name <you@example.com>
pkgname=hello
pkgver=2.12.1
pkgrel=1
pkgdesc="GNU Hello, a program that prints a friendly greeting"
arch=('x86_64')
url="https://www.gnu.org/software/hello/"
license=('GPL-3.0-or-later')
depends=('glibc')
makedepends=('gcc')
source=("https://ftp.gnu.org/gnu/hello/hello-${pkgver}.tar.gz")
sha256sums=('SKIP') # replace with real checksum, or use updpkgsums
build() {
cd "$srcdir/$pkgname-$pkgver"
./configure --prefix=/usr
make
}
package() {
cd "$srcdir/$pkgname-$pkgver"
make DESTDIR="$pkgdir" install
}
The entire POINT of AUR is that anyone can add a script for something they find useful. It can then be voted on by members for consideration to move into an official repo. From the above it's pretty clear that the onus for security and reviewing code is ENTIRELY on the user, and it's almost impossible to imagine that a compromised build script would just pick up votes and make it to a repo.
So in summary AUR is exactly like your Gentoo compile scripts.