motivewave

maintainer xavierbaez · 5 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt binary .deb from downloads.motivewave.com, which is the official vendor download host for the MotiveWave trading application (not a personal or unofficial mirror). The sha512sum is present and pins the specific build. However, the package installs a closed-source, prebuilt binary application from a proprietary vendor's download server — this is a legitimate supply-chain concern because: (1) the binary is executed code, not data; (2) it comes from a vendor-controlled host rather than a well-audited distribution channel; (3) the .deb contains a run.sh script that is symlinked into /usr/bin and executed at runtime. This is a standard pattern for proprietary AUR packages (similar to google-chrome, spotify, etc.) and the checksum provides integrity verification. The risk is real but typical for this class of package — if the vendor's server were compromised or the build_id content swapped, the checksum would catch it. Rating remains MEDIUM as it is an executed binary from a non-standard (though official vendor) host, consistent with AUR proprietary binary package norms.

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:13 source=("${pkgname}-${pkgver}.deb::https://downloads.motivewave.com/builds/${_build_id}/motivewave_${pkgver}_amd64.deb")

MEDIUM AI review 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 binary .deb from downloads.motivewave.com, which is the official vendor download host for the MotiveWave trading application (not a personal or unofficial mirror). The sha512sum is present and pins the specific build. However, the package installs a closed-source, prebuilt binary application from a proprietary vendor's download server — this is a legitimate supply-chain concern because: (1) the binary is executed code, not data; (2) it comes from a vendor-controlled host rather than a well-audited distribution channel; (3) the .deb contains a run.sh script that is symlinked into /usr/bin and executed at runtime. This is a standard pattern for proprietary AUR packages (similar to google-chrome, spotify, etc.) and the checksum provides integrity verification. The risk is real but typical for this class of package — if the vendor's server were compromised or the build_id content swapped, the checksum would catch it. Rating remains MEDIUM as it is an executed binary from a non-standard (though official vendor) host, consistent with AUR proprietary binary package norms.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer:  <xavierbaez at gmail dot com>
    
      2# Contributor: Patrik Sundberg <patrik.sundberg at gmail dot com>
    
      3
    
      4pkgname=motivewave
    
      5pkgver=6.9.12
    
      6pkgrel=1
    
      7pkgdesc="Advanced trading and charting application."
    
      8arch=('x86_64')
    
      9url="https://www.motivewave.com"
    
      10license=('custom')
    
      11depends=('bc' 'ffmpeg' 'gtk2' 'gtk3' 'java-runtime' 'xorg-xrandr')
    
      12_build_id=524
    
      13source=("${pkgname}-${pkgver}.deb::https://downloads.motivewave.com/builds/${_build_id}/motivewave_${pkgver}_amd64.deb")
    
      14sha512sums=('028b72a30526a1a6181b887e3bd7458b65506c382db7f8251a5b043520147849849147533945a3ae6dd42c9a5c6c19f61e91e68d78c42cde2deb557383b50a15')
    
      15
    
      16package() {
    
      17    bsdtar -xf data.tar.xz --no-same-owner -C "$pkgdir/"
    
      18
    
      19    chmod -R g-w "$pkgdir/usr"
    
      20    chown -R root:root "$pkgdir"
    
      21    mkdir -pv "$pkgdir/usr/bin"
    
      22    ln -sv "/usr/share/motivewave/run.sh" "$pkgdir/usr/bin/motivewave"
    
      23    install -Dm644 -t "$pkgdir/usr/share/licenses/$pkgname" "$pkgdir/usr/share/$pkgname/license.html"
    
      24}
    
      25

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