zxtune-bin

maintainer andrewlin16 · 4 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged This package downloads a precompiled binary tarball from storage.zxtune.ru, which is the official storage/CDN host for the ZXTune project (the project's own domain, matching the upstream URL zxtune.bitbucket.io). The host is not a random personal server — it is the project's own infrastructure. However, the package installs a precompiled binary with only an MD5 checksum (which is cryptographically weak and provides minimal integrity assurance), and there is no GPG signature verification. The binary is executed directly on the user's system. This is a legitimate upstream project with its own distribution host, but the lack of strong integrity verification (no SHA256/SHA512, no GPG) for an executed binary from a non-package-manager source keeps this at medium risk rather than clean. The cheaper model's concern about the host being 'unofficial' is partially a false positive since it is the project's own domain, but the weak checksum on an executed binary is a genuine, if modest, supply-chain concern.

Triggered rules

MEDIUM source=() URL on a non-standard host 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:20 source=("https://storage.zxtune.ru/builds/public/r5100/linux/x86_64/zxtune_${pkgver}_linux_x86_64.tar.gz")

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): This package downloads a precompiled binary tarball from storage.zxtune.ru, which is the official storage/CDN host for the ZXTune project (the project's own domain, matching the upstream URL zxtune.bitbucket.io). The host is not a random personal server — it is the project's own infrastructure. However, the package installs a precompiled binary with only an MD5 checksum (which is cryptographically weak and provides minimal integrity assurance), and there is no GPG signature verification. The binary is executed directly on the user's system. This is a legitimate upstream project with its own distribution host, but the lack of strong integrity verification (no SHA256/SHA512, no GPG) for an executed binary from a non-package-manager source keeps this at medium risk rather than clean. The cheaper model's concern about the host being 'unofficial' is partially a false positive since it is the project's own domain, but the weak checksum on an executed binary is a genuine, if modest, supply-chain concern.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Andrew Lin <andrewlin16 at gmail dot com>
    
      2
    
      3pkgname=zxtune-bin
    
      4pkgver=r5100
    
      5pkgrel=2
    
      6pkgdesc="Portable toolkit for ZX-Spectrum music playing (pre-compiled)"
    
      7arch=(x86_64)
    
      8url="https://zxtune.bitbucket.io/"
    
      9license=(GPL3)
    
      10depends=(boost-libs gcc-libs qt5-base zlib)
    
      11optdepends=(
    
      12  'alsa-lib: for ALSA output support'
    
      13  'lame: for conversion to .mp3 format'
    
      14  'libvorbis: for conversion to .ogg format'
    
      15  'flac: for conversion to .flac format'
    
      16  'curl: for accessing data via network schemes'
    
      17)
    
      18provides=(zxtune)
    
      19conflicts=(zxtune-git)
    
      20source=("https://storage.zxtune.ru/builds/public/r5100/linux/x86_64/zxtune_${pkgver}_linux_x86_64.tar.gz")
    
      21md5sums=('88674efc799d2b3f0d9102b90b76981e')
    
      22
    
      23package() {
    
      24  cp -r usr "${pkgdir}/usr"
    
      25}
    
      26
    
      27# vim:set ts=2 sw=2 et:
    
      28

Scan history

Scanned at (UTC)	Severity	Rules
2026-08-03 00:08:14	MEDIUM	2
2026-08-02 00:16:08	MEDIUM	2
2026-08-01 00:11:18	MEDIUM	2
2026-07-31 00:14:10	MEDIUM	2
2026-07-30 00:17:23	MEDIUM	2
2026-07-29 00:25:53	MEDIUM	2
2026-07-28 00:07:28	MEDIUM	2
2026-07-27 00:24:32	MEDIUM	2
2026-07-26 00:07:32	MEDIUM	2
2026-07-25 00:13:44	MEDIUM	2
2026-07-24 00:02:28	MEDIUM	2
2026-07-23 00:14:47	MEDIUM	2
2026-07-22 00:29:32	MEDIUM	2
2026-07-21 00:24:15	MEDIUM	2
2026-07-20 00:19:49	MEDIUM	2
2026-07-19 00:17:08	MEDIUM	2
2026-07-18 00:14:48	MEDIUM	2
2026-07-17 00:06:16	MEDIUM	2
2026-07-16 00:05:41	MEDIUM	2
2026-07-15 00:09:25	MEDIUM	2