jumpman
The PKGBUILD installs a prebuilt binary tarball (Jumpman_lin.tar.gz) from cat.runhello.com, which is a subdomain of the game's official site (runhello.com). The url field confirms runhello.com is the upstream vendor. However, 'cat.runhello.com' is an unusual subdomain (not a standard release host like releases.* or downloads.*), and the package installs the binary directly to /opt without compilation. The sha256sum provides integrity checking, which mitigates tampering risk somewhat, but the binary is executed directly from an unofficial-looking subdomain of the vendor. The depends_x86_64 using lib32-* and the i686/x86_64 arch support with a single binary tarball suggests this is a 32-bit prebuilt binary being run on both architectures. This is a legitimate supply-chain concern (prebuilt binary from a personal/unofficial host) but not clearly malicious — the domain appears to be the actual upstream vendor's infrastructure. The sha256sum check provides meaningful protection against in-transit tampering. This is a borderline medium/clean case; the subdomain is unusual but appears to be the vendor's own hosting.
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:16
source=('http://cat.runhello.com/Jumpman_lin.tar.gz' "${pkgname}.sh" "${pkgname}.desktop")
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD installs a prebuilt binary tarball (Jumpman_lin.tar.gz) from cat.runhello.com, which is a subdomain of the game's official site (runhello.com). The url field confirms runhello.com is the upstream vendor. However, 'cat.runhello.com' is an unusual subdomain (not a standard release host like releases.* or downloads.*), and the package installs the binary directly to /opt without compilation. The sha256sum provides integrity checking, which mitigates tampering risk somewhat, but the binary is executed directly from an unofficial-looking subdomain of the vendor. The depends_x86_64 using lib32-* and the i686/x86_64 arch support with a single binary tarball suggests this is a 32-bit prebuilt binary being run on both architectures. This is a legitimate supply-chain concern (prebuilt binary from a personal/unofficial host) but not clearly malicious — the domain appears to be the actual upstream vendor's infrastructure. The sha256sum check provides meaningful protection against in-transit tampering. This is a borderline medium/clean case; the subdomain is unusual but appears to be the vendor's own hosting.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Chris Severance aur.severach aATt spamgourmet dott com
# Contributor: Lukas Jirkovsky <l.jirkovsky@gmail.com>
# TODO: needs a better icon
set -u
pkgname='jumpman'
pkgver='1.0.2'
pkgrel='2'
pkgdesc='An addictve retro-style game'
arch=('i686' 'x86_64')
url='http://runhello.com/'
license=('custom')
depends_i686=('freetype2' 'glu' 'libgl' 'mesa' 'pcre' 'sdl' 'libpulse')
depends_x86_64=("${depends_i686[@]/#/lib32-}" 'lib32-alsa-plugins')
source=('http://cat.runhello.com/Jumpman_lin.tar.gz' "${pkgname}.sh" "${pkgname}.desktop")
sha256sums=('f803df52902999b76b551b338ff61f7048787cdbada863ff4a8bf80ce212348c'
'00453d83415cbebe45bd600b6be28bbe065a76721e179adb93c4824ba9689c6a'
'934636c213556ab597d546a502b5a9c3c39998ed188b9c4efd583cf72af4217a')
package() {
set -u
install -Dpm644 'Jumpman/Readme.txt' "${pkgdir}/usr/share/licenses/${pkgname}/Readme"
install -d "${pkgdir}/opt"
mv Jumpman "${pkgdir}/opt/${pkgname}"
install -Dpm755 "${pkgname}.sh" "${pkgdir}/usr/bin/${pkgname}"
install -Dpm644 "${srcdir}/${pkgname}.desktop" -t "${pkgdir}/usr/share/applications/"
set +u
}
set +u
# vim:set ts=2 sw=2 et:
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 |