lmstudio-beta

maintainer hansjwulff · 2 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
View on AUR ↗
Why flagged This PKGBUILD downloads a prebuilt binary .deb from installers.lmstudio.ai, which is the official LM Studio distribution host (lmstudio.ai is the vendor's domain, and installers.lmstudio.ai is their CDN/installer endpoint). The sha256 checksum is pinned. The pattern is identical to many legitimate proprietary software AUR packages (e.g., zoom, slack, discord) that pull vendor-provided .deb files. The host is not unofficial or personal — it is the vendor's own infrastructure. However, since this is a closed-source prebuilt binary executed directly on the user's system with no source verification possible beyond the checksum, and the host could theoretically serve different content if compromised, the supply-chain concern is real but inherent to all proprietary binary packages. This is standard practice for proprietary software in the AUR and does not represent an elevated threat beyond what is normal for such packages. The cheaper model's MEDIUM rating is technically defensible but overstates the risk relative to comparable accepted AUR packages. I rate this clean/low — the pattern is normal for proprietary vendor-distributed software, the checksum is present, and the host is the vendor's own domain.

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:19 source=("$filename::https://installers.lmstudio.ai/linux/x64/${pkgver}-1/LM-Studio-${pkgver}-1-x64.deb")
MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): This PKGBUILD downloads a prebuilt binary .deb from installers.lmstudio.ai, which is the official LM Studio distribution host (lmstudio.ai is the vendor's domain, and installers.lmstudio.ai is their CDN/installer endpoint). The sha256 checksum is pinned. The pattern is identical to many legitimate proprietary software AUR packages (e.g., zoom, slack, discord) that pull vendor-provided .deb files. The host is not unofficial or personal — it is the vendor's own infrastructure. However, since this is a closed-source prebuilt binary executed directly on the user's system with no source verification possible beyond the checksum, and the host could theoretically serve different content if compromised, the supply-chain concern is real but inherent to all proprietary binary packages. This is standard practice for proprietary software in the AUR and does not represent an elevated threat beyond what is normal for such packages. The cheaper model's MEDIUM rating is technically defensible but overstates the risk relative to comparable accepted AUR packages. I rate this clean/low — the pattern is normal for proprietary vendor-distributed software, the checksum is present, and the host is the vendor's own domain.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: jeryd leuck <jerydleuck@gmail.com>
2# Contributor: envolution <envolution at mesh dot xyz>
3# Contributor: SoleSoul
4
5pkgname=lmstudio-beta
6_appname=lm-studio
7pkgver=0.4.14
8pkgrel=1
9pkgdesc="Discover, download, and run local LLMs (Professional Beta Repack)"
10arch=('x86_64')
11url="https://lmstudio.ai/"
12license=('LicenseRef-EULA')
13depends=('alsa-lib' 'at-spi2-core' 'atk' 'cairo' 'dbus' 'expat' 'gcc-libs' 'glib2' 'gtk3' 'hicolor-icon-theme' 'libcups' 'libdrm' 'libx11' 'libxcb' 'libxcomposite' 'libxdamage' 'libxext' 'libxfixes' 'libxi' 'libxkbcommon' 'libxrandr' 'libxrender' 'libxshmfence' 'mesa' 'nss' 'pango')
14optdepends=('cuda: NVIDIA GPU acceleration'
15 'rocm-core: AMD GPU acceleration')
16provides=('lmstudio')
17conflicts=('lmstudio-beta-appimage')
18filename="LM-Studio-${pkgver}-1-x64.deb"
19source=("$filename::https://installers.lmstudio.ai/linux/x64/${pkgver}-1/LM-Studio-${pkgver}-1-x64.deb")
20sha256sums=('b6a5a61f0058f72f8ad77ceaa6a669b473303f304574ea8f0ba54ccf60e68ee2')
21
22package() {
23 # Extract data.tar.xz from the debian package
24 bsdtar -xOf "$srcdir/$filename" data.tar.xz | bsdtar -C "$pkgdir" -xv
25
26 # Fix permissions for chrome-sandbox (required for Electron sandboxing)
27 chmod 4755 "$pkgdir/opt/LM-Studio/chrome-sandbox"
28
29 # Create symlink for terminal access
30 install -d "$pkgdir/usr/bin"
31 ln -s /opt/LM-Studio/lm-studio "$pkgdir/usr/bin/lmstudio-beta"
32 ln -s /opt/LM-Studio/lm-studio "$pkgdir/usr/bin/lms-beta"
33
34 # Fix the icon path (the .deb uses usr/share/icons/hicolor/0x0/...)
35 install -d "$pkgdir/usr/share/icons/hicolor/512x512/apps"
36 mv "$pkgdir/usr/share/icons/hicolor/0x0/apps/lm-studio.png" \
37 "$pkgdir/usr/share/icons/hicolor/512x512/apps/lmstudio-beta.png"
38 rmdir "$pkgdir/usr/share/icons/hicolor/0x0/apps"
39 rmdir "$pkgdir/usr/share/icons/hicolor/0x0"
40
41 # Fix the desktop file
42 mv "$pkgdir/usr/share/applications/lm-studio.desktop" "$pkgdir/usr/share/applications/lmstudio-beta.desktop"
43 sed -i 's/^Name=.*/Name=LM Studio Beta/' "$pkgdir/usr/share/applications/lmstudio-beta.desktop"
44 sed -i "s|^Exec=.*|Exec=/usr/bin/lmstudio-beta %U|" "$pkgdir/usr/share/applications/lmstudio-beta.desktop"
45 sed -i 's/^Icon=.*/Icon=lmstudio-beta/' "$pkgdir/usr/share/applications/lmstudio-beta.desktop"
46
47 # Install License
48 install -Dm644 "$pkgdir/opt/LM-Studio/LICENSE.electron.txt" "$pkgdir/usr/share/licenses/$pkgname/LICENSE.electron"
49}
50

Scan history

Scanned at (UTC)SeverityRules
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

Report a package

Reports go to the AURWatch maintainer (one person) and are read by hand. No login required.

0 / 4000
Your suggestion