aleo-studio-bin

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

• PKGBUILD:10 source=("https://aleo-studio-releases.sfo2.digitaloceanspaces.com/latest/aleo-studio_latest_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 binary .deb from a DigitalOcean Spaces bucket (aleo-studio-releases.sfo2.digitaloceanspaces.com) using a 'latest' URL that is not pinned to a specific version. The md5sums check is present but MD5 is cryptographically weak and, more critically, the URL points to a mutable 'latest' artifact — meaning the checksum will mismatch on any update, but more importantly the source can be silently swapped at the bucket level without a URL change. The package then extracts and installs the binary content directly into pkgdir. This is a classic -bin package pattern, but the combination of: (1) a mutable 'latest' URL rather than a versioned release URL, (2) a personal/project-controlled cloud storage bucket rather than an official distribution channel like GitHub releases, and (3) installation of opaque prebuilt binaries constitutes a genuine medium supply-chain risk. The pkgver() function dynamically extracts the version from the downloaded artifact, which is unusual and confirms the floating 'latest' nature of the source. This is not clearly malicious but represents a real concern about artifact substitution.