picoscope

MEDIUM

maintainer mti 13 votes scanned 2026-09-17 00:27:14.276658

View on AUR

Why flagged

The PKGBUILD downloads a prebuilt Debian binary package (.deb) from labs.picotech.com, which is the official PicoTech Linux software repository (the vendor's own apt repository for their oscilloscope software). This is a legitimate vendor host, not a random personal or unofficial mirror. However, the package installs a prebuilt binary blob (a .deb containing a Mono/.NET GUI application plus native libraries) directly into the system, and the integrity check uses only MD5 (weak, though present). The core concern is that this is executed/installed binary code from a vendor-controlled but externally-hosted binary repository — if labs.picotech.com were compromised or the file substituted, the MD5 check provides minimal protection. This is a standard pattern for proprietary hardware vendor software in the AUR (similar to many other hardware driver/GUI packages), but the combination of prebuilt binary + weak checksum + external host keeps it at medium rather than clean. There is no obfuscation, no piracy, and the package appears functional.

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:29 "http://labs.picotech.com/debian/pool/main/p/${pkgname}/${pkgname}_${pkgver//_/-}_all.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 Debian binary package (.deb) from labs.picotech.com, which is the official PicoTech Linux software repository (the vendor's own apt repository for their oscilloscope software). This is a legitimate vendor host, not a random personal or unofficial mirror. However, the package installs a prebuilt binary blob (a .deb containing a Mono/.NET GUI application plus native libraries) directly into the system, and the integrity check uses only MD5 (weak, though present). The core concern is that this is executed/installed binary code from a vendor-controlled but externally-hosted binary repository — if labs.picotech.com were compromised or the file substituted, the MD5 check provides minimal protection. This is a standard pattern for proprietary hardware vendor software in the AUR (similar to many other hardware driver/GUI packages), but the combination of prebuilt binary + weak checksum + external host keeps it at medium rather than clean. There is no obfuscation, no piracy, and the package appears functional.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Mikael Tillenius <mti at tillenius dot com>
    
      2# Thanks to aAXEe <axel at brasshack dot de> and Alexandre Bique (abique)
    
      3# for earlier work.
    
      4pkgname=picoscope
    
      5pkgver=6.14.36_4r5676
    
      6pkgrel=1
    
      7pkgdesc="gui for picotech oscilloscope"
    
      8arch=('x86_64')
    
      9url="http://www.picotech.com/linux.html"
    
      10license=('custom')
    
      11groups=()
    
      12depends=(gtk-sharp-2 libpicoipp desktop-file-utils)
    
      13optdepends=('libps2000: support for picoscope 2000 series'
    
      14		'libps2000a: support for picoscope 2000 series'
    
      15        'libps3000: support for picoscope 3000 series'
    
      16        'libps5000: support for picoscope 4000 series'
    
      17        'libps5000: support for picoscope 5000 series'
    
      18        'libps5000a: support for picoscope 5000a series'
    
      19        'libps6000: support for picoscope 6000 series'
    
      20        )
    
      21provides=()
    
      22conflicts=()
    
      23replaces=()
    
      24backup=()
    
      25options=(!strip)
    
      26install=picoscope.install
    
      27changelog=
    
      28source=(
    
      29  "http://labs.picotech.com/debian/pool/main/p/${pkgname}/${pkgname}_${pkgver//_/-}_all.deb"
    
      30  "picoscope.install"
    
      31  "95-pico.rules")
    
      32md5sums=('71323416628f5d5e06200cb4e44e1d37'
    
      33         '503df69f2e6001e3e9269970a552af13'
    
      34         'afedfca88c003ead013c18f26f789fd4')
    
      35
    
      36package() {
    
      37  tar -xf data.tar.xz -C "${pkgdir}"
    
      38  mkdir -p $pkgdir/etc/udev/rules.d/
    
      39  install -m644 95-pico.rules $pkgdir/etc/udev/rules.d/
    
      40  chmod -R go-w $pkgdir
    
      41  chown -R root:root $pkgdir
    
      42
    
      43  mkdir -p $pkgdir/usr/bin
    
      44  ln -s /opt/picoscope/bin/picoscope $pkgdir/usr/bin/picoscope
    
      45}
    
      46

Scan history

Scanned at (UTC)	Severity	Rules
2026-09-17 00:27:14	Medium	2
2026-09-16 00:03:17	Medium	2
2026-09-15 00:25:31	Medium	2
2026-09-14 00:27:57	Medium	2
2026-09-13 00:19:54	Medium	2
2026-09-12 00:25:17	Medium	2
2026-09-11 00:19:22	Medium	2
2026-09-10 00:22:44	Medium	2
2026-09-09 00:04:09	Medium	2
2026-09-08 00:18:08	Medium	2
2026-09-07 00:30:15	Medium	2
2026-09-06 00:17:06	Medium	2
2026-09-05 00:16:27	Medium	2
2026-09-04 00:03:13	Medium	2
2026-09-03 00:15:47	Medium	2
2026-09-02 00:02:31	Medium	2
2026-09-01 00:11:19	Medium	2
2026-08-31 00:19:57	Medium	2
2026-08-30 00:04:14	Medium	2
2026-08-29 00:29:17	Medium	2