usd-fbx
The PKGBUILD downloads a prebuilt FBX SDK installer binary from autodesk.net (damassets.autodesk.net), which is Autodesk's official CDN/asset delivery domain. The URL pattern matches Autodesk's known FBX SDK distribution URLs. However, the binary is an executable installer that is run directly in prepare() with 'printf yes|n | ./fbx..._linux', meaning an untrusted binary is executed during the build. The sha512sum for the git source is SKIP'd (non-ideal but common for VCS sources), while the FBX tarball does have a checksum. The real concern is: (1) the FBX SDK installer is a prebuilt binary executed at build time, and (2) while damassets.autodesk.net is Autodesk's legitimate CDN, it is not a standard distribution channel like a distro mirror, and the URL could change or be redirected. The checksum on the tarball mitigates the supply-chain risk somewhat. This is a genuine medium: an executed prebuilt binary from a vendor CDN with a checksum but from an unofficial packaging perspective. It is not high because the host is Autodesk's own CDN and a checksum is present, but it is not clean because a prebuilt binary installer is executed during the build process.
Triggered rules
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:20
"https://damassets.autodesk.net/content/dam/autodesk/www/adn/fbx/${_fbxver//./-}/fbx${_fbxver//./}_fbxsdk_linux.tar.gz"
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 FBX SDK installer binary from autodesk.net (damassets.autodesk.net), which is Autodesk's official CDN/asset delivery domain. The URL pattern matches Autodesk's known FBX SDK distribution URLs. However, the binary is an executable installer that is run directly in prepare() with 'printf yes|n | ./fbx..._linux', meaning an untrusted binary is executed during the build. The sha512sum for the git source is SKIP'd (non-ideal but common for VCS sources), while the FBX tarball does have a checksum. The real concern is: (1) the FBX SDK installer is a prebuilt binary executed at build time, and (2) while damassets.autodesk.net is Autodesk's legitimate CDN, it is not a standard distribution channel like a distro mirror, and the URL could change or be redirected. The checksum on the tarball mitigates the supply-chain risk somewhat. This is a genuine medium: an executed prebuilt binary from a vendor CDN with a checksum but from an unofficial packaging perspective. It is not high because the host is Autodesk's own CDN and a checksum is present, but it is not clean because a prebuilt binary installer is executed during the build process.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Adrià Cabello <adro.cc79 at protonmail dot com>
_fbxver=2020.3.4
pkgname=usd-fbx
pkgver=0.1
pkgrel=2
pkgdesc='FBX plugin for USD'
arch=(x86_64)
url='https://github.com/Remedy-Entertainment/usdFBX'
license=('Apache')
depends=(usd
python
boost
gcc)
makedepends=(cmake)
options=(!lto)
source=("git+$url.git"
"https://damassets.autodesk.net/content/dam/autodesk/www/adn/fbx/${_fbxver//./-}/fbx${_fbxver//./}_fbxsdk_linux.tar.gz"
)
sha512sums=('SKIP'
'3cacaf23f43887942366a6cdc1d60bcca813bc1e137b3f9b0870ca80f4e505f4dc1f093f8a625075ba610318e09cb5f74d9fd94c53a05310ac3938b3c9e03d35')
prepare() {
cd "${srcdir}"
#FBX SDK
mkdir -p fbx-sdk
printf "yes\nn\n" | "${srcdir}/fbx${_fbxver//./}_fbxsdk_linux" "${srcdir}/fbx-sdk"
}
build() {
_CMAKE_FLAGS+=(
-DCMAKE_INSTALL_PREFIX=/usr/lib/usd/plugin
-DUSD_CONFIG_FILE=/usr/lib/cmake/pxr/pxrConfig.cmake
-DADSK_FBX_LOCATION="${srcdir}"/fbx-sdk
-DUSDFBX_BUILD_TESTS=ON
)
cmake -S usdFBX -B build -G Ninja "${_CMAKE_FLAGS[@]}"
ninja -C build ${MAKEFLAGS:--j12}
}
package() {
mkdir -p "${pkgdir}"/usr/lib/usd/plugin
cp -r "${srcdir}"/build/plugins/usdFbx "${pkgdir}"/usr/lib/usd/plugin/usdFbx
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 2026-11-01 00:21:48 | Medium | 2 |
| 2026-10-31 00:07:41 | Medium | 2 |
| 2026-10-30 00:29:30 | Medium | 2 |
| 2026-10-29 00:13:55 | Medium | 2 |
| 2026-10-28 00:06:54 | Medium | 2 |
| 2026-10-27 00:23:28 | Medium | 2 |
| 2026-10-26 00:12:40 | Medium | 2 |
| 2026-10-25 00:20:48 | Medium | 2 |
| 2026-10-24 00:14:55 | Medium | 2 |
| 2026-10-23 00:02:19 | Medium | 2 |
| 2026-10-22 00:13:10 | Medium | 2 |
| 2026-10-21 00:12:50 | Medium | 2 |
| 2026-10-20 00:10:31 | Medium | 2 |
| 2026-10-19 00:03:55 | Medium | 2 |
| 2026-10-18 00:06:55 | Medium | 2 |
| 2026-10-17 00:21:55 | Medium | 2 |
| 2026-10-16 00:12:47 | Medium | 2 |
| 2026-10-15 00:28:05 | Medium | 2 |
| 2026-10-14 00:06:47 | Medium | 2 |
| 2026-10-13 00:23:45 | Medium | 2 |