hws

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://w3s.link/ipfs/bafybeiai6vgnd5z2lgyrjbq2luvhbxcihlmbr67dtsdrt6wpsylm5z7ftu/hws-debian-3.1.00-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 IPFS content-addressed gateway (w3s.link). The key point is that IPFS CIDs are content-addressed: the CID 'bafybeiai6vgnd5z2lgyrjbq2luvhbxcihlmbr67dtsdrt6wpsylm5z7ftu' cryptographically identifies the exact content, so the content itself cannot be silently swapped (unlike a mutable URL). However, w3s.link is a third-party IPFS gateway (web3.storage), not the official vendor distribution channel (sentrysoftware.com). The .deb is a prebuilt binary that gets installed and executed, and it is sourced from an unofficial/personal host rather than the vendor's own infrastructure. The md5sums check provides only weak integrity verification. The combination of: (1) executed binary/library content, (2) sourced from a non-official third-party host, and (3) only MD5 integrity checking (though partially mitigated by IPFS CID immutability) constitutes a genuine medium-severity supply-chain concern — the original pinned content could itself be malicious or tampered before pinning. The PKGBUILD also has a minor functional issue (data.tar.xz extraction happens without first extracting the .deb), but this is a packaging bug rather than a security issue.