sfptool-bin

One or more source=() URLs point to a host outside the trusted allowlist (github.com, gitlab.com, codeberg.org, pypi.org, …).

• PKGBUILD:12 source=("sfp-tool_1.4.2_amd64.deb::https://s3.jonasled.de/sfp-tool/linux/x86_64/sfp-tool_1.4.2_amd64.deb")

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD downloads a prebuilt x86_64 binary (.deb) from a personal S3 bucket (s3.jonasled.de) rather than an official distribution channel or the project's own GitHub releases. The binary is extracted and installed directly without any additional verification beyond the sha256sum. While the sha256sum provides integrity checking against accidental corruption or simple substitution, the host is a personal S3 bucket controlled by the maintainer — if that bucket were compromised or the object replaced, the sha256sum in the PKGBUILD would no longer match and the build would fail, which is a meaningful protection. However, the source is still a prebuilt binary from a non-official/non-auditable host (not a distro mirror, not a GitHub release artifact from the canonical repo), which is a genuine supply-chain concern: users are trusting the maintainer's S3 bucket to serve the correct binary. The project URL points to a Gitea instance (jonasled.dev) which is also personal infrastructure. This is a classic AUR binary package pattern that carries real but not catastrophic supply-chain risk — medium severity is appropriate.