hws
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.
Triggered rules
source_untrusted_domain
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")
llm_review
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.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Gerard de Leeuw <gdeleeuw at leeuwit dot nl>
pkgname=hws
pkgver=3.1.00
pkgrel=4
pkgdesc="Hardware Sentry"
arch=("x86_64")
url="https://www.sentrysoftware.com/docs/hws-doc/${pkgver}/index.html"
license=("custom")
source=("https://w3s.link/ipfs/bafybeiai6vgnd5z2lgyrjbq2luvhbxcihlmbr67dtsdrt6wpsylm5z7ftu/hws-debian-3.1.00-amd64.deb")
md5sums=("921951cf1aa02107499642a78b5adeb4")
package() {
tar -xf data.tar.xz -C "${pkgdir}"
mkdir -p "$pkgdir/usr/share/licenses/$pkgname" "$pkgdir/usr/bin"
install -Dm644 "$pkgdir/opt/hws/lib/LICENSE" "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
mv "$pkgdir/lib" "$pkgdir/usr/lib"
ln -s /opt/hws/bin/hws ${pkgdir}/usr/bin/hws
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 2026-09-17 00:27:14 | Medium | 2 |
| 2026-09-16 00:03:17 | Medium | 2 |
| 2026-09-15 00:25:31 | Medium | 2 |
| 2026-09-14 00:27:57 | Medium | 2 |
| 2026-09-13 00:19:54 | Medium | 2 |
| 2026-09-12 00:25:17 | Medium | 2 |
| 2026-09-11 00:19:22 | Medium | 2 |
| 2026-09-10 00:22:44 | Medium | 2 |
| 2026-09-09 00:04:09 | Medium | 2 |
| 2026-09-08 00:18:08 | Medium | 2 |
| 2026-09-07 00:30:15 | Medium | 2 |
| 2026-09-06 00:17:06 | Medium | 2 |
| 2026-09-05 00:16:27 | Medium | 2 |
| 2026-09-04 00:03:13 | Medium | 2 |
| 2026-09-03 00:15:47 | Medium | 2 |
| 2026-09-02 00:02:31 | Medium | 2 |
| 2026-09-01 00:11:19 | Medium | 2 |
| 2026-08-31 00:19:57 | Medium | 2 |
| 2026-08-30 00:04:14 | Medium | 2 |
| 2026-08-29 00:29:17 | Medium | 2 |