amuletml-bin

MEDIUM

maintainer hydraz 0 votes scanned 2026-09-17 00:27:14.276658

View on AUR

Why flagged

The PKGBUILD downloads and executes a shell script (install-amulet.sh) from a personal/project host (hydraz.semi.works) at build time. The script itself likely fetches and installs a pre-built binary, meaning the actual executed code is not fully auditable from the PKGBUILD alone — the install script could download additional binaries from arbitrary locations at runtime. There is no cryptographic verification beyond an MD5 checksum (which is weak and collision-prone), and no PGP signature. The host is non-standard/personal rather than an official distribution mirror or well-known vendor CDN. This is a genuine supply-chain concern: if the install script or the binaries it fetches are replaced, arbitrary code executes during package installation. The sed fixups suggest the script installs pre-compiled binaries with hardcoded paths, confirming binary execution from an unofficial source. This matches the medium severity definition: executed binaries/compiled code from an unofficial host, not clearly malicious but a real 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:16 source=("https://hydraz.semi.works/amulet/install-amulet.sh")

Medium AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 82%): The PKGBUILD downloads and executes a shell script (install-amulet.sh) from a personal/project host (hydraz.semi.works) at build time. The script itself likely fetches and installs a pre-built binary, meaning the actual executed code is not fully auditable from the PKGBUILD alone — the install script could download additional binaries from arbitrary locations at runtime. There is no cryptographic verification beyond an MD5 checksum (which is weak and collision-prone), and no PGP signature. The host is non-standard/personal rather than an official distribution mirror or well-known vendor CDN. This is a genuine supply-chain concern: if the install script or the binaries it fetches are replaced, arbitrary code executes during package installation. The sed fixups suggest the script installs pre-compiled binaries with hardcoded paths, confirming binary execution from an unofficial source. This matches the medium severity definition: executed binaries/compiled code from an unofficial host, not clearly malicious but a real concern.

PKGBUILD

1 offending line(s) highlighted

      1# This is an example PKGBUILD file. Use this as a start to creating your own,
    
      2# and remove these comments. For more information, see 'man PKGBUILD'.
    
      3# NOTE: Please fill out the license field for your package! If it is unknown,
    
      4# then please put 'unknown'.
    
      5
    
      6# Maintainer: Matheus Magalhães de Alcantara <matheus.de.alcantara@gmail.com>
    
      7pkgname=amuletml-bin
    
      8provides=('amuletml')
    
      9conflicts=('amuletml')
    
      10pkgver=0.4.0.0
    
      11pkgrel=1
    
      12pkgdesc="The Amulet programming language"
    
      13arch=(x86_64)
    
      14url="https://hydraz.semi.works/amulet/"
    
      15license=('BSD')
    
      16source=("https://hydraz.semi.works/amulet/install-amulet.sh")
    
      17noextract=()
    
      18md5sums=('73b8390cf7974c38dcfd850d7810f0c4')
    
      19validpgpkeys=()
    
      20
    
      21package() {
    
      22  env PREFIX=$pkgdir/usr/ bash install-amulet.sh
    
      23  sed -re "s;exec $pkgdir/;exec /;g" -i $pkgdir/usr/bin/amc
    
      24  sed -re "s;exec $pkgdir/;exec /;g" -i $pkgdir/usr/bin/amc-prove
    
      25}
    
      26

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