Repository navigation
aur-scanner 2.2.1
2.2.1 — security fix
Two fixes to change detection and variable resolution, plus dependency updates. Upgrading is recommended for everyone on 2.2.0.
Install or upgrade: paru -S aur-scanner (or yay -S aur-scanner). The tag is GPG-signed and the AUR packages verify it (validpgpkeys).
Security
- Scan history is keyed by the package, not by what its PKGBUILD claims. Baselines were stored under the PKGBUILD's raw
pkgnameline, which the author controls and the parser does not expand. Packages written aspkgname="$_pkgname"shared one record and raised falseDIFF-003warnings about each other, and a package declaring another package's name could replace that package's baseline and silence the next real change. Records are now keyed by the package base the resolver got from the AUR; illegal names are refused, mismatched records are discarded, and old records under illegal names (such as$_pkgname.json) are pruned. Expect one quiet first scan for packages whose record was filed under a different name. Reported by AD, with a clean reproduction. Thank you. - A decoded line break can no longer hide a payload. A
printfvalue containing\n, used once, shifted the resolver's line-aligned output, so a variable-builtcurl | shbelow it could scan clean. Line breaks in substituted values are now flattened. New malicious fixture:newline-shift.
Dependencies
- tokio 1.54.1 (RUSTSEC-2026-0386); futures 0.3.34 and hyper 1.12.0, which drop the unmaintained
pin-utils(RUSTSEC-2026-0441).
Full notes: CHANGELOG.md