foundry-nuke

MEDIUM
maintainer adro 2 votes scanned 2026-09-17 00:27:14.276658
View on AUR
Why flagged

The PKGBUILD downloads a prebuilt binary installer (.tgz containing a .run file) from foundry.com, which is the official vendor domain. However, it then executes that .run binary directly during the package() phase (./Nuke$pkgver-linux-x86_64.run --accept-foundry-eula), which is a real supply-chain concern: a .run installer is an opaque self-extracting binary that runs arbitrary code at install time rather than being inspected/unpacked cleanly. The domain is legitimate (The Foundry is the actual vendor of Nuke), and an md5sum is provided (though MD5 is weak). The main concern is executing a prebuilt binary installer rather than extracting it, which is non-standard packaging practice and carries inherent risk if the upstream binary were ever compromised. This is a genuine medium: executed binary from a vendor host, not clearly malicious but not clean packaging either.

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:14 source=($pkgname-$pkgver.tgz::https://www.foundry.com/products/download_product?file=Nuke$pkgver-linux-x86_64.tgz)
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 installer (.tgz containing a .run file) from foundry.com, which is the official vendor domain. However, it then executes that .run binary directly during the package() phase (./Nuke$pkgver-linux-x86_64.run --accept-foundry-eula), which is a real supply-chain concern: a .run installer is an opaque self-extracting binary that runs arbitrary code at install time rather than being inspected/unpacked cleanly. The domain is legitimate (The Foundry is the actual vendor of Nuke), and an md5sum is provided (though MD5 is weak). The main concern is executing a prebuilt binary installer rather than extracting it, which is non-standard packaging practice and carries inherent risk if the upstream binary were ever compromised. This is a genuine medium: executed binary from a vendor host, not clearly malicious but not clean packaging either.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: Adrià Cabello <adro.cc79 at protonmail dot com>
2pkgname=foundry-nuke
3_pkgver_major=15
4_pkgver_minor=1
5_pkgver_build=5
6pkgver=${_pkgver_major}.${_pkgver_minor}v${_pkgver_build}
7pkgrel=1
8pkgdesc="Nuke is a node-based digital compositing and visual effects application"
9arch=('x86_64')
10license=('Custom: The Foundry')
11provides=('nuke')
12depends=('libxcrypt-compat')
13url="https://www.foundry.com/products/nuke"
14source=($pkgname-$pkgver.tgz::https://www.foundry.com/products/download_product?file=Nuke$pkgver-linux-x86_64.tgz)
15md5sums=('88aaaba3b7840f4dc5e851b48e62be41')
16
17package() {
18 mkdir -p "${pkgdir}/opt"
19 mkdir -p "${pkgdir}/usr/bin"
20
21 ./Nuke$pkgver-linux-x86_64.run --accept-foundry-eula
22
23 mv "Nuke$pkgver" "${pkgdir}/opt/nuke"
24
25 ln -s "/opt/nuke/Nuke${_pkgver_major}.${_pkgver_minor}" "${pkgdir}/usr/bin/nuke"
26}
27

Scan history

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

Report a package

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

0 / 4000
Your suggestion