amazon-ecs-init

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

• PKGBUILD:12 source=(https://s3.us-east-1.amazonaws.com/amazon-ecs-agent-us-east-1/${pkgname}-${pkgver}-${pkgrel}.amd64.deb)

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The package downloads a prebuilt binary .deb from an AWS S3 bucket (amazon-ecs-agent-us-east-1). This is actually Amazon's official distribution channel for the ECS agent/init package — Amazon publishes these artifacts to their own S3 buckets as part of the official release pipeline, so this is not a personal or unofficial host. However, the package installs prebuilt binaries (ECS agent daemon, volume plugin, systemd services) extracted from a .deb without source compilation, and uses only an MD5 checksum (weak, collision-prone) rather than SHA256. The prepare() step also only extracts data.tar.xz without first extracting the .deb container properly (missing the ar extraction step), which is slightly broken but the deb may already be partially extracted. The core concern is that prebuilt binaries from any host — even an official one — represent a supply-chain risk if the S3 bucket were compromised or the object replaced, and MD5 provides inadequate integrity protection. This is a real medium-severity concern: executed binaries from a non-GitHub/non-source host with weak checksums, even if the host is plausibly official.