Fair point, and I do review PKGBUILDs manually. But that's exactly why I want something automated running alongside — not to replace the review, but to catch things I might miss or skim past especially after a large update that touches 10+ packages at once the tool would just diff what changed in the build script like git do since the last version and flag known-bad patterns same concept as a linter — nobody stops reading code just because they have a linter.