rootchat-bin
The PKGBUILD downloads a prebuilt AppImage from installer.rootapp.com, which appears to be the official vendor's CDN/installer host for rootapp.com. The AppImage is executed during prepare() via --appimage-extract to unpack it, and the resulting binaries are installed. The sha256sum is pinned, which mitigates MITM risk, but the URL points to a mutable path (Root.AppImage without version in the path), meaning the checksum could become stale or the file could be silently replaced at the source. This is a standard pattern for binary AppImage packages in the AUR, but the non-versioned URL means the checksum is the only integrity guarantee. The host (installer.rootapp.com) is plausibly the official vendor infrastructure. Overall this is a legitimate medium-risk pattern: executed binary from a vendor host with a fixed checksum but a mutable URL — not clearly malicious, but a real supply-chain concern if the host or the file is ever substituted.
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:13
source=("Root-${pkgver}.AppImage::https://installer.rootapp.com/installer/Linux/X64/Root.AppImage")
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD downloads a prebuilt AppImage from installer.rootapp.com, which appears to be the official vendor's CDN/installer host for rootapp.com. The AppImage is executed during prepare() via --appimage-extract to unpack it, and the resulting binaries are installed. The sha256sum is pinned, which mitigates MITM risk, but the URL points to a mutable path (Root.AppImage without version in the path), meaning the checksum could become stale or the file could be silently replaced at the source. This is a standard pattern for binary AppImage packages in the AUR, but the non-versioned URL means the checksum is the only integrity guarantee. The host (installer.rootapp.com) is plausibly the official vendor infrastructure. Overall this is a legitimate medium-risk pattern: executed binary from a vendor host with a fixed checksum but a mutable URL — not clearly malicious, but a real supply-chain concern if the host or the file is ever substituted.
PKGBUILD
1 offending line(s) highlighted# Maintainer: cloudwithax <heyimnick14@gmail.com>
pkgname=rootchat-bin
pkgver=0.9.84
pkgrel=1
pkgdesc="A community platform combining chat with task management, raid planning, and customizable apps"
arch=('x86_64')
url="https://rootapp.com"
license=('custom')
depends=('zlib' 'gcc-libs' 'glibc' 'fuse2')
provides=('rootchat')
conflicts=('rootchat')
options=('!strip' '!debug')
source=("Root-${pkgver}.AppImage::https://installer.rootapp.com/installer/Linux/X64/Root.AppImage")
sha256sums=('06a5564ccaaf38eab76f6a3a0e49cca2db822028a1d1a7be2dafd9a8f47bf4f9')
noextract=("Root-${pkgver}.AppImage")
prepare() {
chmod +x "${srcdir}/Root-${pkgver}.AppImage"
"${srcdir}/Root-${pkgver}.AppImage" --appimage-extract
}
package() {
install -dm755 "${pkgdir}/opt/${pkgname}"
cp -r "${srcdir}/squashfs-root/usr/bin/"* "${pkgdir}/opt/${pkgname}/"
install -dm755 "${pkgdir}/usr/bin"
ln -s "/opt/${pkgname}/Root" "${pkgdir}/usr/bin/rootchat"
install -Dm644 "${srcdir}/squashfs-root/Root.png" "${pkgdir}/usr/share/pixmaps/rootchat.png"
install -Dm644 /dev/stdin "${pkgdir}/usr/share/applications/rootchat.desktop" <<EOF
[Desktop Entry]
Type=Application
Name=Root
Comment=Community platform combining chat with task management and customizable apps
Exec=rootchat
Icon=rootchat
Terminal=false
StartupWMClass=Root
Categories=Network;InstantMessaging;
EOF
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 2026-11-01 00:21:48 | Medium | 2 |
| 2026-10-31 00:07:41 | Medium | 2 |
| 2026-10-30 00:29:30 | Medium | 2 |
| 2026-10-29 00:13:55 | Medium | 2 |
| 2026-10-28 00:06:54 | Medium | 2 |
| 2026-10-27 00:23:28 | Medium | 2 |
| 2026-10-26 00:12:40 | Medium | 2 |
| 2026-10-25 00:20:48 | Medium | 2 |
| 2026-10-24 00:14:55 | Medium | 2 |
| 2026-10-23 00:02:19 | Medium | 2 |
| 2026-10-22 00:13:10 | Medium | 2 |
| 2026-10-21 00:12:50 | Medium | 2 |
| 2026-10-20 00:10:31 | Medium | 2 |
| 2026-10-19 00:03:55 | Medium | 2 |
| 2026-10-18 00:06:55 | Medium | 2 |
| 2026-10-17 00:21:55 | Medium | 2 |
| 2026-10-16 00:12:47 | Medium | 2 |
| 2026-10-15 00:28:05 | Medium | 2 |
| 2026-10-14 00:06:47 | Medium | 2 |
| 2026-10-13 00:23:45 | Medium | 2 |